skill-creator
Guide for creating effective skills that extend agent capabilities with specialized knowledge, workflows, or tool integrations. Use this skill when the user asks to: (1) create a new skill, (2) make a skill, (3) build a skill, (4) set up a skill, (5) initialize a skill, (6) scaffold a skill, (7) update or modify an existing skill, (8) validate a skill, (9) learn about skill structure, (10) understand how skills work, or (11) get guidance on skill design patterns. Trigger on phrases like \"create a skill\", \"new skill\", \"make a skill\", \"skill for X\", \"how do I create a skill\", or \"help me build a skill\".
langgraph-docs
Use this skill for requests related to LangGraph in order to fetch relevant documentation to provide accurate, up-to-date guidance.
web-research
Use this skill for requests related to web research; it provides a structured approach to conducting comprehensive web research
xiaohongshu-posting
小红书自动发帖工具包，通过AutoGLM控制手机自动化发布小红书笔记。当用户请求在小红书发布内容、创建帖子或自动化发帖流程时使用此技能。提供两种发帖模式（普通笔记和长文）的分步指导，确保内容格式正确和UI导航准确。
arxiv-search
Search arXiv preprint repository for papers in physics, mathematics, computer science, quantitative biology, and related fields
second-opinions
Use when wanting independent perspectives from external models (Codex, Gemini) on code, plans, docs, or any task — or when the user asks for a second opinion, codex review, or gemini review
magi
Use only when the user explicitly requests brainstorming, evaluating architecture choices, or comparing options where no single concern dominates
magi-ex
Use when brainstorming ideas, features, or directions for a project where independent perspectives from different model families (Claude/Codex/Gemini) would surface blind spots and spark creative options the user hasn't considered — especially "what cool things can I add", "what should I build next", "give me ideas for X"
sync-skills
(hal-9000) Use when a skill in skills/ has its name or description changed, or is added or removed — syncs README.md, settings.json, and hal_dotfiles.json
bump-hal-voice-version
(hal-9000) Use when editing any file under plugins/hal-voice/ to bump the plugin version before committing
commit
Use when making any git commit. All git add and commit operations must go through this skill, including from subagents and other skills. Always pass a brief description of what changed as the argument
update-allowed-tools
Use when creating or editing a skill that uses Bash commands, external tools, or skill invocations and the allowed-tools frontmatter may be incomplete
skill-builder
Use this skill when creating new Claude Code skills from scratch, editing existing skills to improve their descriptions or structure, or converting Claude Code sub-agents to skills. This includes designing skill workflows, writing SKILL.md files, organizing supporting files with intention-revealing names, and leveraging CLI tools and Node.js scripting.
ant-design
Decision guide for antd 6.x, Ant Design Pro 5/ProComponents, Ant Design X v2, and the offline `@ant-design/cli`. Use for component selection, theming/tokens, SSR, a11y, performance, routing/access/CRUD, AI/chat UI patterns, local API lookup, debugging, migration, and usage analysis.
antd
>
hono
Use when building Hono web applications or when the user asks about Hono APIs, routing, middleware, JSX, validation, testing, or streaming. TRIGGER when code imports from 'hono' or 'hono/*', or user mentions Hono. Use `npx hono request` to test endpoints.
swarm
Orchestrate parallel Claude Code worker swarms with protocol-based behavioral governance. Use for complex features, large refactors, or multi-step tasks. Supports behavioral constraints, parallel workers, and persistent state across context compactions.
promptminder-cli
Use when running promptminder or promptminder-agent commands, setting PROMPTMINDER_TOKEN, passing --team for workspace scoping, handling JSON stderr errors like "Missing token" or HTTP 401, or using the agent wrapper with dot-notation actions and --input JSON.
do-not-repeat-yourself
Find and reuse the nearest correct mechanism before adding another. Use when a Dverity change would add reusable code, policy, or workflow meaning.
resolving-merge-conflicts
Resolve an in-progress merge or rebase conflict from proven product intent. Use only when Git reports an actual conflict.
postmortem
Recall or record confirmed reusable failure lessons. Use after a verified recurrence, review escape, failed gate, or explicit user request.
dverity-repair
Diagnose and repair confirmed defects to Verified Local. Use for evidence-first bug repair; remote submission requires separate explicit authority.
merge-remote-review
Review and land one authenticated provider-native review item. Use when current-head review, landing, closeout, and remote-main parity are in scope.
git-commit
Create narrow auditable local commits. Use when verified Dverity work must be staged and committed without absorbing unrelated changes.
dverity-research
Gather evidence for Dverity repair decisions. Use when a repair hypothesis or boundary needs primary-source proof before mutation.
dverity-simplify
Simplify verified changes before remote submission. Use for deletion-first, YAGNI, native-library, structural, and test-seam review.
submit-remote-review
Submit a named verified source for remote review. Use when explicit authority covers push and one review item, but not approval or landing.
latex-paper-en
English LaTeX academic paper assistant for existing `.tex` projects. Use this skill whenever the user wants to compile, lint, audit, or improve an English LaTeX conference or journal paper such as IEEE, ACM, Springer, NeurIPS, or ICML submissions. Trigger even when the user only mentions one paper issue, such as bibliography errors, grammar cleanup, sentence splitting, logic review, literature review rewriting, related-work restructuring, research-gap derivation, expression polishing, translation, title optimization, figure checks, pseudocode review, algorithm block cleanup, de-AI editing, experiment-section review, table structure validation, three-line table generation, abstract structure diagnosis, or journal adaptation. Also trigger for "proofread my paper", "fix my LaTeX", "prepare for submission", "check my manuscript", "improve my writing", "rewrite related work", "research gap", "related work is too list-like", "three-line table", "booktabs", "check abstract", "reformat for another journal", "换投", `algorithm2e`, `algorithmicx`, `algpseudocodex`, `Require/Ensure`, or "Algorithm 1" when the user has a .tex file.
paper-audit
Deep-review-first audit for Chinese and English academic papers across LaTeX, Typst, and PDF formats. Use whenever the user wants reviewer-style paper critique, pre-submission readiness checks, pass/fail gate decisions, structured revision roadmaps, journal-style peer review reports, or re-audits of revised manuscripts. Trigger even if the user only says "review my paper", "check if this is ready to submit", "audit this PDF", "simulate peer review", "write a SCI review report", "give me Summary / Major Issues / Minor Issues / Recommendation", "find the biggest problems in this manuscript", or "re-check whether I fixed the review issues". Do not use for direct source editing or compilation-heavy repair; route those to the format-specific writing skills instead.
latex-thesis-zh
Chinese LaTeX thesis assistant for existing .tex degree thesis projects (XeLaTeX/LuaLaTeX/latexmk). Use this skill whenever a user works on a Chinese master's or doctoral thesis needing compilation, GB/T 7714 bibliography checks, chapter structure mapping, template detection (thuthesis, pkuthss), terminology consistency, logic coherence review, literature review restructuring, related-work synthesis, research-gap derivation, heading lead-in checks, title optimization, de-AI editing, experiment chapter review, three-line table validation, or abstract structure diagnosis. Trigger even for single issues like "帮我编译论文", "检查国标格式", "看看绪论逻辑", "文献综述太像罗列", "研究空白没推出来", "毕业论文", "学位论文", "硕士/博士论文", "三线表", "检查摘要", or "摘要结构".
typst-paper
Typst academic paper assistant for existing `.typ` paper projects in English or Chinese. Use this skill whenever the user wants to compile, audit, or improve a Typst paper, including format checks, bibliography validation for BibTeX or Hayagriva, grammar/sentence/logic review, literature review rewriting, related-work restructuring, research-gap derivation, expression polishing, translation, title optimization, pseudocode review, algorithm block cleanup, de-AI editing, experiment-section review, table structure validation, three-line table generation, abstract structure diagnosis, or journal adaptation. Trigger even when the user only mentions one Typst file, one bibliography issue, one pseudocode block, one section rewrite, "rewrite related work", "research gap", "three-line table", "check abstract", or "reformat for another journal". Also trigger when the user mentions ".typ files", "typst compile error", "typst export", "typst bibliography", `algorithm-figure`, `lovelace`, or `algorithmic` even without saying the word "Typst" explicitly.
industrial-ai-research
>
tikhub-api-helper
Search and query TikHub APIs for TikTok, Douyin, Xiaohongshu, Lemon8, Instagram, YouTube, Twitter, Reddit, and more. Use when user asks about needs to fetch data from social media platforms. Supports both English and Chinese queries.
finding-triage
Interactively validate and triage Hacktron findings against the actual source code and (optionally) a live deployment, separate true positives from false positives, adjust severity, then either propose fixes and commit them or set the finding's state in Hacktron (true_positive, false_positive, accepted_risk, resolved). Talks to the Hacktron REST API with curl, reading the latest API docs at runtime. Use when the user asks to validate, triage, confirm, filter, or fix Hacktron scan or PR-review findings, or mentions false positives in a Hacktron scan.
patch-diff-analyzer
Specialized in reverse-engineering compiled binaries (JARs, DLLs). Use this when the user asks to compare versions, find security fixes, or analyze binary patches.
zafer-skills
Expo React Native mobile app development with RevenueCat payments, AdMob ads, i18n localization, onboarding flow, paywall, and NativeTabs navigation
issue-tree-builder
McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components. Use when users need to decompose strategic questions, structure analysis, create work plans, or prepare for case interviews. Apply hypothesis-driven approach to problem-solving.
scpr-framework
SCPR (Situation-Complication-Problem-Recommendation) framework for structured problem solving and executive communication. Use when users need to structure strategic arguments, analyze business situations, create executive summaries, or develop clear problem statements using McKinsey-style communication. Apply when structuring recommendations, writing memos, or organizing strategic thinking.
storyline-builder
McKinsey-style storyline framework for building presentation decks. Use when users need to structure presentations, pitch decks, or strategic communications. Creates logical flow where each storyline becomes a slide title, progressing from problem to solution.
mckinsey-critic
Reviews decks, documents, and strategies like a McKinsey engagement manager. Grades each section, flags structural problems, and gives the top 3 fixes. Use after building a deck, writing a strategy doc, or outlining a recommendation — before it goes to stakeholders.
workshop-designer
Design a half-day or full-day strategy workshop that ends with a committed decision and named owners — not a "great discussion" with no artifact. Outputs an hour-by-hour agenda, breakout prompts with expected outputs, pre-reads, facilitator playbook for when things go sideways, and the post-workshop artifact that justifies the day. Use for offsites, leadership alignment sessions, kickoff workshops, planning meetings >2 hours.
top-down-memo
Answer-first writing using the Minto Pyramid Principle. Lead with the conclusion, then 2–4 MECE supporting arguments, then evidence under each. Use whenever you have a recommendation, finding, or assessment to communicate in writing — memos, emails to execs, Slack updates that need to land, briefing docs. Different from the Decision Memo Builder (which is a specific 1-page decision artifact); this is the general writing method.
synthesis
Force the "so what" out of a messy pile of raw inputs — interview notes, customer transcripts, survey results, research dumps, meeting recordings — into 3 insights with evidence and implication. Use when you have more data than you have meaning, and someone is about to ask "ok, so what does this mean?" Different from summarization; output must change how the reader acts.
stakeholder-map
Map the people who can make or break a decision onto a Power/Interest grid, with each named stakeholder's stance (champion / skeptic / blocker / unknown), what they care about, and the single influence move you'll make for them. Use before any cross-functional decision, big launch, reorg, or executive ask — anywhere the politics will decide the outcome more than the merits.
meeting-prep-kit
Personal meeting prep tool. Given a meeting (attendees, topic, desired outcome), generates a tight prep packet — 3-bullet pre-read, time-boxed agenda, your top 3 talking points, and the top 3 objections you'll face with rebuttals. Use before any meeting where you're driving an outcome — exec reviews, stakeholder pitches, scope negotiations, manager 1:1s with an ask, vendor calls.
mckinsey-charts
Generate McKinsey-style consulting charts as native python-pptx objects (editable inside PowerPoint). Three workhorse types — bar+callout for TAM/single-number stories, stacked column over time for revenue/usage mix, and waterfall for drivers/bridge analysis. Use when you need a chart that looks like it came from an EM-reviewed deck, not from Excel defaults.
hypothesis-tree
Build a Day-1 hypothesis tree — your best-guess answer to the governing question, broken into 2–3 supporting sub-hypotheses, with the test that would prove or kill each one. Different from an issue tree (which decomposes the problem space). This commits to an answer before you do the work, so the work targets what would actually change your mind. Use at the start of any analysis where you'd otherwise "boil the ocean."
deck-pipeline
Multi-agent pipeline that builds a polished presentation deck from a single topic. Four agents work in sequence — Strategist defines the narrative, Builder creates the deck, Critic reviews it like a McKinsey EM, Fixer applies the top fixes. Use when you need a presentation that survives senior audiences.
decision-memo-builder
Builds a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA — brutal brevity, SCP storyline clarity, decision-forcing output, evidence density. Use when drafting a memo for a leadership decision, a scope cut, a buy/build/partner call, a roadmap slip, or any "should we X?" moment that needs a yes/no from a specific person by a specific date.
ai-use-case-scorer
Score and prioritize AI use cases for your own job. Given a list of candidate use cases (or a description of your workflow), evaluates each on Value × Feasibility × Safety and tiers them — Do Now / Do This Quarter / Park / Avoid. Use when you've heard "we should use AI more" and need to figure out what to actually build first. Built for the individual IC, not org-wide rollout.
Page 674 of 1719 · 85906 results
