Loading...
Loading...
Found 2,206 Skills
Verify that claims and direct quotes in research manuscripts are present in source materials. Systematically checks interview transcripts, datasets, or cited literature using fast search with haiku agent fallback for intensive reading.
OAuth 2.0/2.1 specification expert with deep RFC knowledge and Fastify integration patterns
Internal skill. Use cc10x-router for all development tasks.
Multi-AI Parallel Deep Research. Triggered when users need comprehensive research, in-depth study, multi-party comparison, or comprehensive analysis covering multiple dimensions and sources for a certain topic. Suitable for complex topics (technical selection, competitor analysis, industry trends, controversial topics, etc.), not suitable for simple fact queries. Conduct parallel research through multiple AI services, cross-validate, and output a comprehensive report with citations.
Validate documentation files for completeness, accuracy, and consistency with the codebase. Use when user mentions "check documentation", "validate docs", "is the README up to date?", requests documentation review, says "docs are wrong" or "fix the docs", or is working on documentation improvements. Covers README files, API docs, CHANGELOG, and any markdown documentation.
Validate Claude Code plugin structure, manifests, frontmatter, and dependencies. Use when user mentions "validate plugin", "check plugin health", "plugin broken", "plugin not loading", "plugin errors", "plugin.json invalid", "agent not working", "check plugin structure", or reports plugin-related issues.
AQE skill
AQE skill
Run the localization workflow: extract strings, validate localization readiness, check for hardcoded text, and generate translation-ready string tables.
Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
Evaluate and validate Claude Code rules in .claude/rules/ directories. Use when auditing rule file quality, validating frontmatter and glob patterns, or checking rules organization before deployment. Do not use when writing new rules from scratch - use rule authoring guides instead. Do not use when evaluating skills or hooks - use skills-eval or hooks-eval instead.
Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.