[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MHT99951GFBMYS46AGP3DX":3,"skill-same:01M6MHT99951GFBMYS46AGP3DX":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6MHT99951GFBMYS46AGP3DX","krypton-planning",null,"Use when a user has a feature request, bugfix, refactor, migration, architecture change, or product goal and needs an implementation plan before coding. Use especially when wrong ownership, duplicate paths, stale contracts, weak evidence, or unclear cutover would make plausible agent work dangerous.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjturntdev\u002Fkrypton\u002Fskills\u002Fkrypton-planning\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"planning","krypton planning","goal","when","request","implementation plan","make","paths","bugfix","feature","feature request","contracts","change","evidence","use","work","coding","plan","refactor","product","architecture","2026-11-10 10:12:30",false,"---\nname: krypton-planning\ndescription: Use when a user has a feature request, bugfix, refactor, migration, architecture change, or product goal and needs an implementation plan before coding. Use especially when wrong ownership, duplicate paths, stale contracts, weak evidence, or unclear cutover would make plausible agent work dangerous.\n---\n\n# Krypton Planning\n\nKrypton Planning turns a request into a goal package that names the outcome, truth owner, contract, cutover, and acceptance evidence before anyone writes code.\n\n## Core Rule\n\nDo not treat a task list as a plan. A Krypton plan is ready only when it answers:\n\n```text\nWhat outcome are we serving?\nWhat current behavior is being replaced, redirected, deleted, or demoted?\nWho owns the truth?\nWhat contract crosses the boundary?\nWhat is the smallest high-value slice?\nWhat proves the result from the target person's perspective?\nWhat kill criteria stop duplicate paths from living forever?\n```\n\nIf ownership, cutover, contract, or evidence is fuzzy, stop and map before planning.\n\n## Workflow\n\n1. Write the outcome contract:\n\n```text\nPlan title:\nIntent:\nCurrent behavior:\nExpected outcome:\nTarget-perspective output:\nTruth owner:\nContract boundary:\nCutover:\nDisplaced path:\nValue density:\nEvidence gate:\nAcceptance evidence:\nEvidence lane:\nKill criteria:\nNon-goals:\nRisk if wrong:\n```\n\n2. Map the architecture slice before tasks:\n\n```text\nFiles to create:\nFiles to modify:\nFiles to avoid:\nSource of truth:\nRead path:\nWrite path:\nContract boundary:\nIntegration points:\nMigration\u002Fcutover:\nDisplaced path:\nAcceptance evidence gate:\n```\n\nFor broad or unclear repositories, dispatch a read-only explorer if the harness supports agents. Ask one bounded question, such as \"map the source of truth, read\u002Fwrite path, unsafe files, and evidence gate.\" The execution session should use this map instead of rediscovering the same slice.\n\n3. Save a goal package unless the user gives another location:\n\n```text\ndocs\u002Fgoals\u002F\u003Cgoal-slug>\u002FPLAN.md\ndocs\u002Fgoals\u002F\u003Cgoal-slug>\u002FGOAL.md\ndocs\u002Fgoals\u002F\u003Cgoal-slug>\u002FEVIDENCE.md\n```\n\n`PLAN.md` contains the full plan. `GOAL.md` is a short execution prompt that points to the plan instead of copying it. `EVIDENCE.md` starts empty and is filled during execution with the real proof captured from the target perspective.\n\n4. Start `PLAN.md` with this header shape:\n\n```markdown\n# [Outcome Title] Implementation Plan\n\n**Intent:** ...\n**Current Behavior:** ...\n**Expected Outcome:** ...\n**Target-Perspective Output:** ...\n**Truth Owner:** ...\n**Contract Boundary:** ...\n**Cutover:** ...\n**Displaced Path:** ...\n**Value Density:** ...\n**Evidence Gate:** ...\n**Acceptance Evidence:** ...\n**Evidence Lane:** ...\n**Kill Criteria:** ...\n**Architecture Slice:** ...\n**Plan Review Gate:** Requires PRE review before execution.\n```\n\n5. Break work into small tasks. Each task names exact files, allowed scope, expected output, verification command, acceptance evidence, and whether it can run in parallel.\n\n6. Run a PRE plan review when possible. Use `plan-reviewer-prompt.md` as the individual prompt template. Do not execute until blocker findings are fixed or explicitly accepted by the user.\n\n## GOAL.md Shape\n\nUse this compact handoff. This is the `\u002Fgoal` prompt or next-session prompt the operator should paste into Codex or Claude:\n\n```markdown\n# Goal: [Outcome Title]\n\nUse Krypton Execution to execute `docs\u002Fgoals\u002F\u003Cgoal-slug>\u002FPLAN.md`.\n\nCore rules:\n- Treat PLAN.md as the source plan.\n- Preserve intent, ownership, contract, cutover, evidence, and kill criteria.\n- Do not add a new dominant path without deleting, redirecting, demoting, or shimming the displaced path.\n- Capture acceptance evidence from the target perspective and record it in EVIDENCE.md.\n- Say \"implemented but unproven\" if that evidence cannot be captured.\n```\n\n## EVIDENCE.md Shape\n\nCreate this file with the goal package and update it during execution:\n\n```markdown\n# [Outcome Title] Evidence\n\n## Acceptance Evidence\n\nRecord the real artifact that proves the outcome from the target perspective.\n\n## Verification\n\nRecord the focused check that passed, including the command and relevant output.\n\n## Review Notes\n\nRecord reviewer, maintainer, or verifier findings that changed the result.\n```\n","# Krypton Planning\n\nKrypton Planning turns a request into a goal package that names the outcome, truth owner, contract, cutover, and acceptance evidence before anyone writes code.\n\n## Core Rule\n\nDo not treat a task list as a plan. A Krypton plan is ready only when it answers:\n\n```text\nWhat outcome are we serving?\nWhat current behavior is being replaced, redirected, deleted, or demoted?\nWho owns the truth?\nWhat contract crosses the boundary?\nWhat is the smallest high-value slice?\nWhat proves the result from the target person's perspective?\nWhat kill criteria stop duplicate paths from living forever?\n```\n\nIf ownership, cutover, contract, or evidence is fuzzy, stop and map before planning.\n\n## Workflow\n\n1. Write the outcome contract:\n\n```text\nPlan title:\nIntent:\nCurrent behavior:\nExpected outcome:\nTarget-perspective output:\nTruth owner:\nContract boundary:\nCutover:\nDisplaced path:\nValue density:\nEvidence gate:\nAcceptance evidence:\nEvidence lane:\nKill criteria:\nNon-goals:\nRisk if wrong:\n```\n\n2. Map the architecture slice before tasks:\n\n```text\nFiles to create:\nFiles to modify:\nFiles to avoid:\nSource of truth:\nRead path:\nWrite path:\nContract boundary:\nIntegration points:\nMigration\u002Fcutover:\nDisplaced path:\nAcceptance evidence gate:\n```\n\nFor broad or unclear repositories, dispatch a read-only explorer if the harness supports agents. Ask one bounded question, such as \"map the source of truth, read\u002Fwrite path, unsafe files, and evidence gate.\" The execution session should use this map instead of rediscovering the same slice.\n\n3. Save a goal package unless the user gives another location:\n\n```text\ndocs\u002Fgoals\u002F\u003Cgoal-slug>\u002FPLAN.md\ndocs\u002Fgoals\u002F\u003Cgoal-slug>\u002FGOAL.md\ndocs\u002Fgoals\u002F\u003Cgoal-slug>\u002FEVIDENCE.md\n```\n\n`PLAN.md` contains the full plan. `GOAL.md` is a short execution prompt that points to the plan instead of copying it. `EVIDENCE.md` starts empty and is filled during execution with the real proof captured from the target perspective.\n\n4. Start `PLAN.md` with this header shape:\n\n```markdown\n# [Outcome Title] Implementation Plan\n\n**Intent:** ...\n**Current Behavior:** ...\n**Expected Outcome:** ...\n**Target-Perspective Output:** ...\n**Truth Owner:** ...\n**Contract Boundary:** ...\n**Cutover:** ...\n**Displaced Path:** ...\n**Value Density:** ...\n**Evidence Gate:** ...\n**Acceptance Evidence:** ...\n**Evidence Lane:** ...\n**Kill Criteria:** ...\n**Architecture Slice:** ...\n**Plan Review Gate:** Requires PRE review before execution.\n```\n\n5. Break work into small tasks. Each task names exact files, allowed scope, expected output, verification command, acceptance evidence, and whether it can run in parallel.\n\n6. Run a PRE plan review when possible. Use `plan-reviewer-prompt.md` as the individual prompt template. Do not execute until blocker findings are fixed or explicitly accepted by the user.\n\n## GOAL.md Shape\n\nUse this compact handoff. This is the `\u002Fgoal` prompt or next-session prompt the operator should paste into Codex or Claude:\n\n```markdown\n# Goal: [Outcome Title]\n\nUse Krypton Execution to execute `docs\u002Fgoals\u002F\u003Cgoal-slug>\u002FPLAN.md`.\n\nCore rules:\n- Treat PLAN.md as the source plan.\n- Preserve intent, ownership, contract, cutover, evidence, and kill criteria.\n- Do not add a new dominant path without deleting, redirecting, demoting, or shimming the displaced path.\n- Capture acceptance evidence from the target perspective and record it in EVIDENCE.md.\n- Say \"implemented but unproven\" if that evidence cannot be captured.\n```\n\n## EVIDENCE.md Shape\n\nCreate this file with the goal package and update it during execution:\n\n```markdown\n# [Outcome Title] Evidence\n\n## Acceptance Evidence\n\nRecord the real artifact that proves the outcome from the target perspective.\n\n## Verification\n\nRecord the focused check that passed, including the command and relevant output.\n\n## Review Notes\n\nRecord reviewer, maintainer, or verifier findings that changed the result.\n```\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fjturntdev\u002Fkrypton\u002Fskills\u002Fkrypton-planning",474,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-11 14:40:14",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill krypton-planning",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill krypton-planning",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill krypton-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjturntdev\u002Fkrypton\u002Fskills\u002Fkrypton-planning\u002FSKILL.md",true,[74,80],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"agents\u002Fopenai.yaml","REFERENCE","参考文档",322,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjturntdev\u002Fkrypton\u002Fskills\u002Fkrypton-planning\u002Fagents\u002Fopenai.yaml",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"plan-reviewer-prompt.md",1235,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjturntdev\u002Fkrypton\u002Fskills\u002Fkrypton-planning\u002Fplan-reviewer-prompt.md",[85,93,100,107,132,157],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":92},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":92},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":45},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[114,115,116,117,118,119,120,121,122,123,124,27,125,126,127,128,36,129,130,131],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","cli","merge","past",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":45},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[139,140,141,128,142,143,144,145,146,147,148,149,150,151,119,152,153,154,155,156],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":170,"publishedAt":45},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[163,166,167],{"categoryNo":164,"categoryName":165,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[159,171,172,173,174,175,176,153,177,120,178,179,180,181,27,182,183,184,185,186],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]