22 skills (repositories by a-ariff) · sorted by popularity
Detects when Claude is uncertain but presenting answers confidently. Teaches Claude to recognize and communicate uncertainty clearly instead of masking it with confident language.
The English summary is being prepared. Showing the original description.
Assign confidence scores (0-100) to every claim in a response. Helps users understand which parts are verified facts and which are educated guesses. Use when the user needs to know how much to trust each part of the answer.
The English summary is being prepared. Showing the original description.
Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.
The English summary is being prepared. Showing the original description.
Multi-angle review of responses before delivery. Audits from 4 perspectives -- factual accuracy, logical consistency, completeness, and safety. Use for high-stakes responses where errors have real consequences.
The English summary is being prepared. Showing the original description.
Use this skill when asked to "validate plugin", "check plugin structure", "verify plugin", "audit plugin", "is my plugin correct", "plugin issues", or when troubleshooting plugin problems.
The English summary is being prepared. Showing the original description.
Use this skill when asked to "create a plugin", "build a new plugin", "make a Claude Code plugin", "scaffold plugin", "plugin structure", "add commands/agents/skills/hooks to plugin", or when helping with plugin development.
The English summary is being prepared. Showing the original description.
Trace bugs backward to their origin, not just symptoms
The English summary is being prepared. Showing the original description.
Use fresh agents for focused subtasks to avoid context pollution
The English summary is being prepared. Showing the original description.
Core skill activation protocol - establishes mandatory workflows for finding and applying skills before any task
The English summary is being prepared. Showing the original description.
Never claim completion without fresh verification evidence
The English summary is being prepared. Showing the original description.
Dispatch to right technique when you hit a wall
The English summary is being prepared. Showing the original description.
Multi-layer validation to catch bugs before they escape
The English summary is being prepared. Showing the original description.
Use this skill when asked about "hooks", "PreToolUse", "PostToolUse", "SessionStart", "hook events", "validate tool use", "block commands", "add context on session start", or implementing event-driven automation.
The English summary is being prepared. Showing the original description.
Complete methodology for preventing AI hallucinations. Use when accuracy is critical and you need Claude to verify before claiming, cite before asserting, and admit uncertainty instead of guessing.
The English summary is being prepared. Showing the original description.
Create detailed implementation plans with bite-sized tasks
The English summary is being prepared. Showing the original description.
Forces every code-related claim to include file:line citations. No citation means the claim must be verified or removed. Use when building documentation, writing code reviews, or any output that others will rely on.
The English summary is being prepared. Showing the original description.
Execute implementation plans in batches with review checkpoints
The English summary is being prepared. Showing the original description.
Memory Sync Skill
The English summary is being prepared. Showing the original description.
Canvas API Connection Skill
The English summary is being prepared. Showing the original description.
Transform rough ideas into solid designs through structured questioning
The English summary is being prepared. Showing the original description.
Verify every claim from multiple independent angles -- code, docs, tests, git history. Use when you need high confidence that something is correct before acting on it.
The English summary is being prepared. Showing the original description.
Ensure every factual claim in a response is backed by verifiable evidence from the codebase, documentation, or external sources. Use when preparing technical documentation, code reviews, or any output where accuracy is non-negotiable.
The English summary is being prepared. Showing the original description.