Loading...
Loading...
Found 11,723 Skills
Code review closeout for Claude Code, Codex, OpenCode, and DeepSeek TUI: local dirty changes, branch vs main, parallel tests.
Use when validating implementation against spec artifacts before archive — not for design, planning, or implementation
Paper Analyst — Responsible for in-depth paper reading, extracting method details, and building comparison tables. Activated when assigned to analyze papers by research supervisors or literature investigators. Conduct structured analysis on the Top 20 core papers, generate paper analysis cards and cross-paper comparison tables.
Generate video summary reports using the VSS video_search_frag extension with Long Video Summarization (LVS), Enterprise RAG knowledge retrieval, and human-in-the-loop parameter collection. Use when: user wants to generate a video summary, report, or analysis using the frag pipeline.
This skill should be used when the user asks to "research a topic", "run-research", "last30", "what's happening with X", "what are people saying about X", "find the best X", "X prompts", "latest on X", "X news", "what are people recommending for X", "research X for me", or wants to know what's trending, discussed, or debated about any subject in recent weeks.
Configure the project's skill stack and supervision preferences. Reads the curated registry in `skillpacks/skill_dictionary.yaml`, asks a short preset-first set of questions about workflow, dependency tolerance, autonomy style, and resource policy, then writes or updates `.co-researcher/skills.yaml`. Trigger phrases: "customize my stack", "configure skillpacks", "set up my skills", "choose presets", "configure supervision and packs", "personalize this project".
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Persistent memory system for Claude Code. Two-layer architecture (hot cache + knowledge wiki), safety hooks, /close-day end-of-day synthesis. Zero external dependencies.
This spell is about representation change, not: - Naming changes (same structure, different identifiers) - Execution changes (same code, different runtime) - Architecture changes (new system design) - Duplication (same thing, different place) The key test: Can you point to a source artifact and a target artifact where the same information is expressed in structurally different ways? If yes → Polymorph.
This spell is archaeology, not history research. It operates on specific artifacts from a specific dead system to answer specific questions. It is NOT general tech history, NOT interviewing living people, and NOT monitoring live systems.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.