Recently active skills
Trending is calculated from star growth this site has recorded itself. No history is estimated or back-filled.
Not enough history yet: 2 of 7 days recorded. Until then this list is ordered by the most recent content change.
21711 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| hyper-planhashgraph-online/awesome-codex-plugins[Hyper] Use this skill when the user asks to plan a change before implementation - a feature, refactor, migration, fix, or multi-step build - and expects a decision-complete plan file that a worker can execute without another interview. It explores read-only, writes only a draft and a plan under `.hyper/`, reviews the plan for gaps, then continues into execution by default unless the user asked for a plan only. Do not use for PRD, spec, or wireframe packages; for immediate edits that need no plan; or for research reports. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| hyper-pptxhashgraph-online/awesome-codex-pluginsUse this skill when the user asks to build, edit, or read a PowerPoint deck - create a .pptx from an outline or analysis, add slide transitions or element animations, change text or fonts in a deck someone else made, remove slides, or open a .pptx and report what each slide says. Write a typed JSON spec, render with a bundled engine to a .pptx plus checked slide images, or inspect an existing deck before touching it. Do not use for slide images only, PDF-only output, Google Slides, or Keynote. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| hyper-prdhashgraph-online/awesome-codex-plugins[Hyper] Use this skill when the user wants a product requirements document for a web, iOS, Android, or desktop product - a new idea to size and write, an existing PRD to revise, or a PRD to review - and expects one `prd.md` file with goals, metrics, scoped stories, EARS requirements, acceptance scenarios, and a handoff block. It decides platform and size first, asks only the decisions the user alone can make within the size's question budget, marks unknowns inline, and stops at the document. Do not use it for user flows, wireframes, diagrams, HTML previews, technical design, task breakdowns, or implementation. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| hyper-reporthashgraph-online/awesome-codex-pluginsUse this skill when the user asks for a report as a finished document rather than a chat answer: a briefing, business or research report, proposal, status or analysis write-up, or one-page summary. It fixes audience and decision up front, keeps every number and claim traceable to a source, and renders one authored Markdown source into HTML, print PDF, per-page PNG/JPG images, DOCX, or Markdown, with tables and figures where they carry the reader. Do not use it for slide decks, spreadsheet workbooks, single generated images, or reports that only need to live in chat. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| hyper-researchhashgraph-online/awesome-codex-plugins[Hyper] Use this skill when the user asks for multi-source, cited research - fact-finding, comparisons, market or trend analysis, or evidence-backed recommendations across live web, official docs, GitHub, and local repo sources - saved as a markdown report. Do not use for one-source lookups, rewriting, or implementation. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| hyper-reviewhashgraph-online/awesome-codex-pluginsUse this skill when a change that already exists needs a verdict - review only a diff, a branch, a pull request, or the working tree, with an independent reviewer, a hands-on QA matrix, and a test-quality and code-smell gate, or review and fix the confirmed blockers when the user explicitly asks for repairs. It binds the verdict to the reviewed content, saves `.hyper/review/[slug].md`, and edits no source file unless the user asked to fix. Do not use it for a change that does not exist yet, a design or look review, a deployment failure, a runtime failure to diagnose, or a one-line wording edit. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| hyper-seohashgraph-online/awesome-codex-plugins[Hyper] Use this skill when the user asks for an SEO, AEO, GEO, or LLMO audit, an optimization report, a new-site launch setup plan, or a score-improvement loop for a named target. Covers on-page, technical, content, Core Web Vitals, answer-engine, generative-engine, AI search visibility, AI crawler policy, metadata, and citation readiness, saved under `.hyper/seo/[slug]/`. Do not use it for page or product design, release gating, pure performance work with no search context, or market research with no target site. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| hyper-skillhashgraph-online/awesome-codex-pluginsUse this skill when the user asks to create or refactor a reusable Codex skill folder, including SKILL.md trigger wording, instruction contracts, rules, references, scripts, assets, and validation checks. Do not use for generic documentation that is not a skill. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| hyper-uiux-designhashgraph-online/awesome-codex-pluginsUse this skill when the user asks to design an app or web screen and wants both a picture of it and the screen as HTML before real code - a login, onboarding, dashboard, or checkout screen, or a short flow of screens, for mobile, tablet, or web, in light or dark. It reads public UI references (UIBowl, Mobbin public pages) for patterns, settles tokens, has hyper-imagegen render one mockup image per screen, then builds one standalone HTML file per screen that matches that mockup, checks the match with a browser screenshot, and saves both with handoff notes under `.hyper/uiux-design/[slug]/`. Do not use it for one image that is not a product screen, a visual-direction brief or audit, production frontend or native code, or a requirements document. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| personal-data-protectionhashgraph-online/awesome-codex-pluginsPersonal-data-protection compliance reference for engineers building applications subject to Singapore PDPA, Indonesia UU PDP, Thailand PDPA, Malaysia PDPA, Philippines DPA (RA 10173), or Vietnam PDPL (91/2025/QH15). Use when reviewing or modifying code that touches personal data — signup/auth/consent, data export, account deletion, retention/purging, admin access to personal-data stores, third-party processors, breach response, or privacy/T&C documents. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-art-designhashgraph-online/awesome-codex-plugins服化道技能。用于设计人物设定提示词、道具设定提示词和场景环境提示词。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-asset-reporthashgraph-online/awesome-codex-pluginsUse when 统计资产/做资产表/分析人物/场景/道具。产出暖金主题HTML资产分析报告。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-bootstraphashgraph-online/awesome-codex-pluginsUse when the user says "用 jimeng-bootstrap 初始化项目", "初始化即梦分镜师", "把当前项目装成即梦分镜师", or asks to bootstrap the plugin workflow. It installs the producer rules and prepares a short-drama project in the current workspace. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-character-assetshashgraph-online/awesome-codex-plugins给短剧建人物资产库(阶段零点五·即梦分镜师)。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-dialogue-assistanthashgraph-online/awesome-codex-pluginsUse when 核对即梦分镜台词本(阶段一)。对照剧本原文校验一致性。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-directorhashgraph-online/awesome-codex-pluginsUse when 做即梦分镜导演分析(阶段二)。拆剧情点、定预算、产出讲戏本。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-global-style-flowhashgraph-online/awesome-codex-pluginsUse when 开新剧需写 config/global-style.md 全局风格 + 制片批注(核心卖点/主线/梗概/人物/制作要求)。与用户共同敲定,不得自定。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-html-viewhashgraph-online/awesome-codex-pluginsHTML 视图生成技能。将即梦分镜提示词(02-jimeng-prompts.md)转换为视觉增强的 HTML 阅读版。作为标准流程步骤,在生成 clean.txt 后自动执行。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-panorama-blockinghashgraph-online/awesome-codex-plugins全景站位分镜技能。基于剧本和本集资产清单,用单一母镜头(≤15秒)输出整集的人物调度关系分镜(全景/零台词/时间轴镜头格式)。在分镜编写之前使用,为即梦分镜提供站位调度依据。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-reviewhashgraph-online/awesome-codex-plugins即梦分镜审核技能。审核母镜头+子镜头结构的即梦分镜提示词。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-script-intakehashgraph-online/awesome-codex-pluginsUse when 新剧本入库即梦分镜师工作空间并拆集。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| jimeng-storyboardhashgraph-online/awesome-codex-pluginsUse when 编写即梦分镜。按讲戏本剧情点映射母镜头、填7字段。 | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| documenthashgraph-online/awesome-codex-pluginsRecord a decision, document existing code, or file a supplied research material, in free text; no first word is a mode. Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, a repeated agent procedure, a user flow with examples over an existing spec, or a finished report or one external material already in hand. Name any document type inside the subject — journey, prd, idea, or cpat included — to get exactly that type. Planning a feature, an investigation not yet done, or an intended user journey the request asks to plan ('plan the onboarding journey') → /archcore:plan. Checking docs against code or docs health → /archcore:review. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| inithashgraph-online/awesome-codex-pluginsFirst-time Archcore setup. Wires the host (MCP config, hooks, CLAUDE.md/AGENTS.md managed block), measures the authored context the repo already holds, then composes a first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for the top hotspot modules — shown in ONE preview and created on a single confirm. Modes, named as the first word: init import converts the repo's authored context — CLAUDE.md, AGENTS.md, .cursor/rules and other agent instructions, ADR and RFC folders, contributor docs, internal pages of a published docs site, recoverable git history — into native typed documents with no import marks, staged by a plan when the volume is large; init refresh adds facts that appeared since, or drills into one domain with init refresh <domain>. Use on a fresh clone, empty `.archcore/`, 'set up archcore', 'migrate our CLAUDE.md to archcore', 'import our docs and ADRs', or to wire host configs. Not for individual docs or planning. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| planhashgraph-online/awesome-codex-pluginsPlan future work, investigate before building, research a topic, or compare the alternatives for a choice. Takes optional free text. The skill reads the request, open drafts, accepted canon, branch, and code, then creates only the documents a later reader needs — none for a small fix. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'plan the onboarding journey', 'investigate X before we plan', 'compare the alternatives for Y', 'REST or a queue? two teams disagree', 'I need market research before we plan', 'we are regulated — trace the requirements'. With no arguments it resumes an open planning draft or offers what to plan next. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| reviewhashgraph-online/awesome-codex-pluginsThe pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; on the default branch it reviews the unpushed and uncommitted work. A bug-hunting code review complements this review and does not replace it. Also use for 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Takes an optional path, tag, topic, or ref in free text; no first word is a mode — say 'are docs out of date', 'audit the knowledge base', 'close out the feature', or 'capture this pattern' in plain words. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| documenthashgraph-online/awesome-codex-pluginsRecord a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| inithashgraph-online/awesome-codex-pluginsFirst-time Archcore setup. Wires the host (MCP config, hooks, CLAUDE.md/AGENTS.md managed block), measures the authored context the repo already holds, then composes a first-day seed — stack rule, run guide, data-model, integrations, config, entry points, public surface, a linked architecture overview, and specs for the top hotspot modules — shown in ONE preview and created on a single confirm. Modes, named as the first word: init import converts the repo's authored context — CLAUDE.md, AGENTS.md, .cursor/rules and other agent instructions, ADR and RFC folders, contributor docs, internal pages of a published docs site, recoverable git history — into native typed documents with no import marks, staged by a plan when the volume is large; init refresh adds facts that appeared since, or drills into one domain with init refresh <domain>. Use on a fresh clone, empty `.archcore/`, 'set up archcore', 'migrate our CLAUDE.md to archcore', 'import our docs and ADRs', or to wire host configs. Not for individual docs or planning. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| planhashgraph-online/awesome-codex-pluginsPlan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research <topic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use /archcore:document. Not for checking docs against code — use /archcore:review. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |
| reviewhashgraph-online/awesome-codex-pluginsThe pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; with no diff, it reports project health. A bug-hunting code review complements this review and does not replace it. Also use for 'show status', 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Modes, named as the first word: drift for staleness detection, deep for a full documentation audit, closeout to close a finished feature, experience to capture a repeated pattern. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review. | Stars: 1.5k | Updated | Claude CodeCodex | Unverified | Install |