Loading...
Loading...
Found 3,074 Skills
Audit whether a repo's docs actually ANSWER the questions a reader has — by spawning fresh, cheap (Haiku) agents that cold-read ONLY the docs and measuring how fast they reach the answer, whether they hit dead-ends, whether they fall back to source code, and whether they cite docs that contradict each other. Use after a doc reorg, when docs "feel scattered," or when the same confusion keeps recurring. Surfaces findability gaps (a corpus can be COMPLETE — every doc indexed — yet not FINDABLE) plus a prioritized fix list. Works on any repo's docs, not just this one.
Use when writing git commit messages for non-trivial changes — captures decision context (constraints, rejected alternatives, confidence, directives) as structured git trailers so future agents and developers can query project knowledge via git log --trailer=
Use this when you need to understand the positioning, capabilities, architecture, or integration process of the Ziniao Browser WebDriver automation interface, for design discussions, integration planning, or tool evaluation. Do not use it for writing specific automation scripts—refer directly to the interfaces and examples in reference/ when executing scripts.
Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.
Document session work with explicit commands. Use /start to begin tracking, /end to finalize session, /clear to reset. Tracks decisions, file changes, and context for continuity.
AI-Driven Specification-Driven Development (SDD) workflow orchestrator - guides skill selection and general SDD methodology
Maintains changelogs following Keep a Changelog format, categorizes changes by type. Use when updating CHANGELOG, preparing releases, or documenting version changes.
Guides Claude in creating well-structured SKILL.md files following best practices. Provides clear guidelines for naming, structure, and content organization to make skills easy to discover and execute.
Guidelines for creating AI agent skills. Use when writing new skills, documenting coding patterns, or reviewing skill files. Triggers when creating or modifying files in the skills/ directory.
Define team interfaces, contracts, and communication boundaries
This skill should be used when the user asks to "document discussion", "save meeting notes", "record conversation", "capture meeting", or mentions needing to document team discussions with participants, decisions, and action items.
Reverse engineer Perplexity AI web APIs — intercept browser traffic, decode undocumented endpoints, map request/response schemas, extract auth flows, and translate discoveries into SDK code.