Loading...
Loading...
Found 1,121 Skills
Loads documents fully into the main agent's context so the agent can answer questions, summarize, or work with that content in subsequent turns. Use whenever the user wants to ingest, read, study, review, absorb, or pull in documents — especially when they say things like "load these docs", "read all of these", "ingest this folder", "pull in these PDFs", "load all docs in X", or paste a list of file paths/URLs and ask you to read them. Handles local files (text, code, markdown, PDFs, notebooks, images), entire folders (recursively), and remote URLs. The skill is single-turn — once the agent reports "DONE", it deactivates until the user invokes it again.
Run a spec-driven agent loop where coding tasks live as markdown specs that move through inbox → active → archive, get implemented by Claude Code or Codex, and pass a review gate before they count as done. Use when the user mentions "loop factory", a "spec-driven loop", an "agent factory", wants repeatable/reviewable agent work, or when a repo has a factory/specs/inbox or factory/specs/active directory. Also covers installing and scaffolding the loop-factory CLI into a project.
Manage Apple Notes on macOS — list, search, read, create, append, move, delete, and export notes, and manage folders. Use when the user mentions Apple Notes / 备忘录, "add a note", "my notes", searching their notes, organizing folders, or exporting a note to Markdown/HTML. macOS-only; runs locally against Notes.app — no cloud API, no token.
Validates the interoperability between skills. Ensures that output formats (JSON/Markdown) from one skill are correctly consumed by the next in a chain.
Design accessibility testing plans and test cases covering WCAG 2.1 standards, screen readers, and keyboard navigation. Default output is Markdown, with support for requesting Excel/CSV/JSON formats. Use for accessibility testing.
Use this skill for multi-model AI code review. Trigger whenever the user asks to review code changes, audit a diff, check code quality, review a PR, review commits, or review uncommitted changes before pushing or merging. Also trigger when they say 'code review', 'review my changes', 'check this before I merge', or want multiple perspectives on code. Runs Codex and Claude reviews in parallel, then synthesizes a unified report. Do NOT use for reviewing documentation, markdown, or non-code files, or for trivial single-line changes.
Collaborative brainstorming partner for multi-session ideation projects. Use when the user wants to brainstorm, ideate, explore ideas, or think through problems—whether for SaaS products, software tools, book ideas, newsletter content, business strategies, or any creative/analytical challenge. Handles session continuity across days/weeks via versioned markdown documents. Includes brainstorming methods catalog and supports both connected (cross-project awareness) and clean-slate modes.
Neovim (LazyVim) configuration via Nix: LSP, plugins, im-select, extraPackages. Mason is disabled; all LSP/formatters/linters are managed by Nix extraPackages. Triggers: "nvim 플러그인", "lazy.nvim", "한글 입력", "im-select", "extraPackages", "Mason 비활성화", "tree-sitter 빌드 오류", "LSP 서버 안 됨", "markdownlint", "Neovim 설정", Mason migration, tree-sitter build errors, lazy-lock.json conflict.
Persistent markdown files as working memory for complex tasks: plan, track progress, store findings. Use when tasks have 3+ phases, require research, span many tool calls, or risk context drift. Use for "plan", "break down", "track progress", "multi-step", or complex tasks. Do NOT use for simple lookups, single-file edits, or questions answerable in one response.
A collection of technical writing rules to significantly improve the quality of your writing. Achieve professional writing quality by eliminating redundant expressions, avoiding repeated sentence endings, correctly distinguishing between kanji and hiragana, using active voice, and placing subjects and predicates close together, among other practices. This must be referenced for all tasks involving text output or generation. Applicable tasks include creating PR descriptions, writing technical documents, design documents, specifications, and procedure manuals, updating README/CLAUDE.md/Confluence pages, generating commit messages, summarizing survey results and specifications, outputting in Markdown, improving and reviewing existing text, etc. This skill is triggered by all requests involving text output, such as "write", "create", "compose", "summarize", "add to", "output", "improve", "review", "document", "create a PR", "output in Markdown", etc. Refer to this skill even for short instructions or implicit text generation tasks. Explicit mention of the skill name is not required.
Competitor intelligence system. Track competitors across Reddit, Twitter/X, and LinkedIn. Run one-time deep research to create competitor profiles, then automate daily/weekly monitoring with consolidated reports and actionable signals. Reports delivered as markdown files and via email.
Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.