c--projects-dashclaw-route-changes
Make focused changes to API routes with verification.
pinned to #dc89c19updated 2 weeks ago
Ask your AI client: “install skills/c-projects-dashclaw-route-changes”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/c-projects-dashclaw-route-changesmetahub onboarded this repo on the author's behalf.
If you own github.com/ucsandman/DashClaw on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
284
Last commit
2 weeks ago
Latest release
published
- #agent-framework
- #agent-governance
- #agent-runtime
- #ai-agents
- #ai-governance
- #ai-infrastructure
- #ai-ops
- #autogen
- #claude-code
- #crew-ai
- #decision-engine
- #developer-tools
- #hermes
- #langchain
- #mcp
- #mcp-server
- #model-context-protocol
- #openclaw
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.dc89c19· 2 weeks ago
Documentation
41Description qualitywarn
8 words · 53 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
26,798 chars · 13 sections · 8 code blocks
Tags / topics declared
18 total — agent-framework, agent-governance, agent-runtime, ai-agents, ai-governance, ai-infrastructure (+12)
README has usage / example sections
found: Quick start
Homepage / docs URL declared
https://www.dashclaw.io/
Release history
1- releasecurrentdc89c19warn2 weeks ago
Contents
Trigger
Use when an HTTP route or server module needs to be added or changed.
Files to inspect first
C:\Projects\DashClaw\app\api-keys\page.jsC:\Projects\DashClaw\appC:\Projects\DashClaw\app\lib\sessionViewer.mjsC:\Projects\DashClaw\app\api\mcp\route.jsC:\Projects\DashClaw\middleware.js
Steps
- Read each file listed above before any edit.
- Establish a verification baseline before any edit.
- Plan the changes — list edits up front.
- Apply edits in one pass; avoid re-reading the same file ≥ 3 times.
- Run the project's verification command; do not declare done until it passes.
Verification gates
- No new high-confidence repeated-run signals in the session's tool sequence.
- No secret-output guard hits.
What not to do
- Don't introduce new abstractions when an existing one fits.
- Don't add error handling for scenarios that can't happen — only at system boundaries.
- Don't widen scope to a refactor when the trigger calls for a focused change.
Generated by AgentLens from session acec7ebd-b7d3-4e21-8582-f9617e66b654 at 2026-05-12T21:42:09.652Z.
Skill candidate distilled from 3 similar prior session(s). Review and edit before relying on it.
Reviews
No reviews yet. Be the first.
Related
orchestration-patterns
>
migration-patterns
>
deployment-sop
>
mh install skills/c-projects-dashclaw-route-changes