Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 27781–27810 of 35192 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| arch-designheliohq/shipSystem-design thinking before any doc or code: goals/non-goals, back-of-envelope numbers, components and contracts, failure modes, operability, security, trade-offs. Use for "design this system", "architecture for X", "trade-offs for X", "how should we architect", "API design", "data model for", "service boundaries", or before an ADR. Hands off to /ship:write-docs to record the decision. Not implementation planning (/ship:design — that turns a decided design into stories). | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| autoheliohq/shipRun Ship's full production workflow from raw requirement to PR: design, dev, E2E, review, QA, refactor, and handoff. Use only for explicit /ship:auto, auto pipeline requests, or end-to-end delivery. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| designheliohq/shipPlan implementation before coding: investigate the repo, write spec and plan, and validate with a peer. Use for "plan", "design approach", "scope", or any coding task needing a plan. Not system-design thinking (/ship:arch-design) or full /ship:auto. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| devheliohq/shipImplement from a spec or plan: extract stories, build in safe waves, test, commit, and get peer review per story. Use for "implement", "build/code this plan", or targeted fix findings. If no plan exists, use /ship:design first. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| e2eheliohq/shipAdd durable end-to-end tests for user/API-visible behavior. Detect or scaffold the E2E framework, write tests, run the app, and store evidence. Use for E2E, Playwright/Cypress, regression tests, or quality gates. Not exploratory QA. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| handoffheliohq/shipShip completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| qaheliohq/shipRuntime QA of a change: start the app, test acceptance criteria and edge cases, and report evidence. Use for "test this", "QA", "does it work", exploratory checks, or post-review runtime verification. Not static code review. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| refactorheliohq/shipImprove existing code without changing behavior: scan smells, simplify, dedupe, reuse utilities, and verify after edits. Use for refactor, cleanup, simplify, reduce duplication, extract method, dead code, or code smells. No PR. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| reviewheliohq/shipStatic code review of the active diff: trace changed paths and report concrete P1/P2/P3 correctness, security, or spec bugs with file:line evidence. Use for code review or bug checks. Not runtime QA. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| use-shipheliohq/shipRoute ambiguous software-delivery requests to the smallest useful Ship workflow: one skill, a phase bundle, or /ship:auto. Use at session start, when the user asks how to use Ship, or when they say build/check/ship without a phase. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| write-docsheliohq/shipCreate or update structured docs under docs/ with frontmatter, numbering, lifecycle status, and index regeneration — guides, references, troubleshooting, design docs and ADRs. Use for "write a doc", "document this", "create a guide", "write an ADR", "update the docs". For the system-design thinking itself (architecture, trade-offs, failure modes) use /ship:arch-design first — it hands back here to record the decision. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| cn-law-hubZongziForu/cn-law-hub用于查询、检索、核验、下载、导出、批量采集中国官方法律法规、规章、条约和具体法条。Use this skill aggressively when the user asks to 查法律、查法规、查条例、查规章、查条约、查法条、查第几条、找法律依据、引用法律依据、核验现行有效、判断是否废止/已修改/尚未生效、下载法规全文、导出法规目录、批量下载法规文件、按关键词检索具体法条、展开法条分析,或在中国法律咨询、案例分析、合规审查、合同审查、劳动争议、行政法分析、公司合规、数据合规、政策研究中需要调用、核验或引用中国现行有效法律法规原文作为依据。Trigger also when phrases such as 依法、依规、依照法律规定、法律法规 imply a need to verify specific statutory authority or article-level text. Covers 国家法律法规数据库 (flk.npc.gov.cn), 国家规章库 (gov.cn), 外交条约库 (treaty.mfa.gov.cn), 国务院政策文件库 (sousuo.www.gov.cn), 司法部行政法规库 (xzfg.moj.gov.cn), 党内法规库 (12371.cn), 国防部法规文库 (mod.gov.cn), 税务法规库 (fgk.chinatax.gov.cn), 生态环境部法规规章 (mee.gov.cn), and 最高人民法院发布栏目 (court.gov.cn). Supports 标题/正文检索, 精确/模糊检索, 时效性过滤, 分类过滤, 分页, 排序, 单篇下载, 批量下载, 法条级抽取, 地区/制定机关分类, and browser fallback. Trigger when the answer may depend on current effective Chinese statutes, regulations, rules, treaties, article text, official document status, or official source attribution. Do not use for purely general legal theory, generic writing, or legal reasoning that does not require retrieving or verifying official Chinese legal documents. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| equalangequalang/equalang-skillTranslate whole files with Equalang, keeping their layout - documents (PDF, DOCX, PPTX, XLSX, EPUB, HTML, TXT), subtitles (SRT, VTT), pictures, and audio or video (which come back as translated subtitles) - and transcribe recordings into timed text. Use when the user points at a FILE or a URL of one and wants it translated or transcribed, or wants strings translated in bulk; not for a sentence you can translate yourself. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| super-pmkonglong87/superPMProduct Manager Skills Pack - Full lifecycle support from demand to delivery 让一个产品经理拥有一个产品团队的能力 Use when: Starting a new product, planning features, analyzing market, designing solutions, managing growth, strategic decision | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-evidence-auditkonglong87/superPMUse when: 审核产品调研、市场分析、增长报告或 PRD 中的关键结论是否有可追溯证据,核对来源、日期、推断与冲突 Do NOT use when: 只需评审 PRD 的完整性和表达(用 pm-prd-review)、仅需撰写新报告而非审查现有主张 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-selfcheckkonglong87/superPMUse when: 需要检查 super-pm 技能包安装完整性、元数据和体积 Do NOT use when: 正在执行具体 PM 任务且不需要安装诊断 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| prompt-pekonglong87/superPMUse when the user explicitly invokes /prompt-pe or explicitly asks to clarify, enhance, or rewrite a vague prompt Do NOT use for ordinary product-management requests; leave existing super-pm/start-super-pm routing unchanged | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-brainstormkonglong87/superPMUse when: 需要创意方案、探索产品方向、发散思维、本质问题分析 用户说"我想做一个XX""帮我规划XX产品""帮我设计一下需求" 用户给出新产品方向,但尚未完成本轮 brainstorm 交互确认 新产品从0到1的第一步 Do NOT use when: 用户明确说"跳过 brainstorm / 直接需求调研 / 已完成头脑风暴" 需求已明确且用户明确要求直接执行具体后续 skill | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-clarifykonglong87/superPMUse when: 有初步需求清单需要细化细节、需明确需求场景和边界条件、需求描述模糊需要结构化 Do NOT use when: 需求已足够详细可直达开发、仅需快速立项无需深入 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-competitorkonglong87/superPMUse when: 需要持续监控竞品动态、建立竞品情报预警、定期输出竞品监控月报、追踪竞品版本/定价/功能/舆情/融资异动 Do NOT use when: 仅需一次性竞品调研(用 pm-market / pm-search --type=competitor);产品尚无明确竞品 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-deep-talkkonglong87/superPMUse when: 用户已有产品想法、方案、计划或待选方案,希望分析利弊、梳理选择标准、补全关键考虑或获得决策建议 用户明确要求“深入聊聊”“分析这个方案”“帮我梳理取舍”“我该怎么选” 用户在 pm-brainstorm 中选定方向后,主动要求进一步讨论其可行性与取舍 Do NOT use when: 用户还没有方向,只想产生多个创意(使用 pm-brainstorm) 用户只需要事实调研、需求验证、市场分析、优先级计算或文档撰写(使用对应 skill) | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-demandkonglong87/superPMUse when: 用户明确要求需求调研、痛点验证,或已有产品需要验证一个具体需求 Do NOT auto-select when: 用户只想发散新产品方向(优先 pm-brainstorm)或只是简短讨论且不需正式调研 Direct /pm-demand requests may proceed with their own evidence checks; a full new-product chain can recommend brainstorm first. | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-interviewkonglong87/superPMUse when: 需要设计用户访谈/用户调研方案、编写访谈提纲、规划样本与招募、制定访谈执行与分析方法 Do NOT use when: 仅做案头需求调研(用 pm-demand);已有明确结论只需验证单一假设且无需访谈 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-journeykonglong87/superPMUse when: 需要理解用户体验全链路、发现用户痛点与机会点、优化用户转化流程 Do NOT use when: 用户流程已非常清晰、仅需单一功能分析而非全局体验 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-marketkonglong87/superPMUse when: 需要了解市场格局与竞争态势、收集行业数据、分析竞品优劣势、评估市场机会 Do NOT use when: 市场已有充分内部调研数据、仅需简单规模估算无需深度分析 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-mvpkonglong87/superPMUse when: 需要确定第一版产品功能范围、已有需求清单需筛选 MVP 功能、需要确定最小可行产品边界 Do NOT use when: 产品已上线需要完整功能集、仅需梳理需求无需裁剪范围 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-poolkonglong87/superPMUse when: 有新需求需要录入跟踪、需求状态需要变更、需要统一管理需求池、需求数量增多需要结构化 Do NOT use when: 需求极少可直接管理、仅需一次性分析无需持续跟踪 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-prioritykonglong87/superPMUse when: 有多个需求需要排定先后顺序、资源有限需决定先做什么、需求冲突需要客观评分 Do NOT use when: 只有一个需求无需排序、优先级已由上级/业务方明确指定 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-searchkonglong87/superPMUse when: 需要进行市场调研数据收集、竞品信息采集、行业舆情监控、合规政策检查 Do NOT use when: 已有完整数据无需补充、仅需内部数据分析无需外部信息 | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |
| pm-brand-motionkonglong87/superPMUse when: 需要为品牌设计动效方向、制作 logo 动画 demo、定义品牌动效性格、从静态 logo 到动态展示的过渡 Do NOT use when: 需要专业级动效交付(应交给设计师)、已有成品动效无需方向验证、仅需要文字描述不需要 demo | Stars: 94 | Updated | Claude CodeCodex | Unverified | Install |