Use before claiming ANY work is complete. Evidence before claims, always. Non-negotiable verification gate.
/plugin marketplace add sharpner/claude-agents/plugin install workflow-core@sharpner-claude-agentsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Core Principle: "Evidence before claims, always."
You MUST execute verification before asserting work is complete, fixed, or passing.
Skipping any step = dishonest reporting.
Before claiming ANY of these, you MUST run fresh commands:
| Claim | Required Command |
|---|---|
| "Tests pass" | npm test / go test ./... / pytest |
| "Build succeeds" | npm run build / go build ./... |
| "Linter is clean" | npm run lint / golangci-lint run |
| "Bug is fixed" | Reproduce steps + verify fix |
| "Feature works" | E2E test or manual verification |
| "Work is complete" | ALL above checks |
Watch for these language patterns that bypass verification:
If you catch yourself using these → STOP → Run verification.
When reporting completion:
**Verification:**
- Command: `npm test`
- Exit code: 0
- Output: 47 tests passed, 0 failed
- Claim confirmed: ✅ All tests pass
"If you lie, you'll be replaced."
Prior failures included:
Trust depends on honest reporting backed by actual evidence.
NO EXCEPTIONS. NO SHORTCUTS.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.