[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKZP9MKJZ4YTD7RHD75KAM":3,"skill-same:01M6MKZP9MKJZ4YTD7RHD75KAM":72},{"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":18,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":61},"01M6MKZP9MKJZ4YTD7RHD75KAM","changelog",null,"Use when the user asks to add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fchangelog\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31],"commits","entries","true","add changelog","keep","Bash","cut","read","release","write","edit","semver","add","2026-11-10 10:12:30",false,"---\nname: changelog\ndescription: \"Use when the user asks to add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.\"\nuser-invocable: true\nallowed-tools: Read, Edit, Write, Bash, AskUserQuestion\n---\n\n# changelog\n\nManage `CHANGELOG.md` per Keep a Changelog 1.1.0 and SemVer 2.0.0:\n\n- **add:** one entry;\n- **from-commits:** derive entries from Conventional Commits;\n- **release:** cut a version.\n\nEdit only `CHANGELOG.md`. Never change version files, commit, or tag; `release` prints suggested commands.\n\n## Step 1 — Resolve the action\n\nResolve `add`, `from-commits` (`commits`), or `release` from `$ARGUMENTS` or the request; ask if ambiguous.\n\n## Step 2 — Pre-flight (all actions)\n\n```bash\nroot=$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull) || root=.\nls \"$root\u002FCHANGELOG.md\" 2>\u002Fdev\u002Fnull\n```\n\nAlways use `$root\u002FCHANGELOG.md`, never a cwd-relative path.\n\n- Existing: read and preserve style.\n- Missing for `add`\u002F`from-commits`: create the standard linked title, intro, and `## [Unreleased]` skeleton.\n- Missing for `release`: stop and suggest `\u002Fchangelog add` or `\u002Fchangelog from-commits`.\n\n## Step 3 — Insert under `[Unreleased]` (add, from-commits)\n\nAppend `- \u003Cimperative description>` to its category under `[Unreleased]`, creating the category in canonical order. Never edit released sections or date `[Unreleased]`.\n\n## Step 4 — Run the action\n\nLoad [writing guidelines](references\u002Fwriting-guidelines.md) for entry rules, commit mapping, and SemVer bumps.\n\n- **add** — use the user's text or ask for one of the six categories and a ≤15-word description; tighten and insert it.\n- **from-commits** — follow the process below.\n- **release** — follow `references\u002Frelease.md`.\n\n### from-commits\n\nThe changelog, not git tags, is the source of truth for what shipped — derive entries, don't mirror the log.\n\n1. **Range:** use `\u003Clatest-tag>..HEAD`; without tags, find the commit for the latest released section. Without either baseline, show the commit count and ask for all, last 30, last 100, or another range. Never silently choose all.\n2. **Gather:** inspect subjects and bodies; breaking footers may be in bodies.\n3. **Derive:** map, filter, aggregate, and deduplicate per the guidelines. Collapse a 10–20-commit feature into 1–3 user-facing entries.\n4. **Confirm:** show grouped proposals plus skipped or aggregated items with reasons, then insert only after approval.\n","# changelog\n\nManage `CHANGELOG.md` per Keep a Changelog 1.1.0 and SemVer 2.0.0:\n\n- **add:** one entry;\n- **from-commits:** derive entries from Conventional Commits;\n- **release:** cut a version.\n\nEdit only `CHANGELOG.md`. Never change version files, commit, or tag; `release` prints suggested commands.\n\n## Step 1 — Resolve the action\n\nResolve `add`, `from-commits` (`commits`), or `release` from `$ARGUMENTS` or the request; ask if ambiguous.\n\n## Step 2 — Pre-flight (all actions)\n\n```bash\nroot=$(git rev-parse --show-toplevel 2>\u002Fdev\u002Fnull) || root=.\nls \"$root\u002FCHANGELOG.md\" 2>\u002Fdev\u002Fnull\n```\n\nAlways use `$root\u002FCHANGELOG.md`, never a cwd-relative path.\n\n- Existing: read and preserve style.\n- Missing for `add`\u002F`from-commits`: create the standard linked title, intro, and `## [Unreleased]` skeleton.\n- Missing for `release`: stop and suggest `\u002Fchangelog add` or `\u002Fchangelog from-commits`.\n\n## Step 3 — Insert under `[Unreleased]` (add, from-commits)\n\nAppend `- \u003Cimperative description>` to its category under `[Unreleased]`, creating the category in canonical order. Never edit released sections or date `[Unreleased]`.\n\n## Step 4 — Run the action\n\nLoad [writing guidelines](references\u002Fwriting-guidelines.md) for entry rules, commit mapping, and SemVer bumps.\n\n- **add** — use the user's text or ask for one of the six categories and a ≤15-word description; tighten and insert it.\n- **from-commits** — follow the process below.\n- **release** — follow `references\u002Frelease.md`.\n\n### from-commits\n\nThe changelog, not git tags, is the source of truth for what shipped — derive entries, don't mirror the log.\n\n1. **Range:** use `\u003Clatest-tag>..HEAD`; without tags, find the commit for the latest released section. Without either baseline, show the commit count and ask for all, last 30, last 100, or another range. Never silently choose all.\n2. **Gather:** inspect subjects and bodies; breaking footers may be in bodies.\n3. **Derive:** map, filter, aggregate, and deduplicate per the guidelines. Collapse a 10–20-commit feature into 1–3 user-facing entries.\n4. **Confirm:** show grouped proposals plus skipped or aggregated items with reasons, then insert only after approval.\n",{"name":5,"description":7,"allowed-tools":37,"user-invocable":38},"Read, Edit, Write, Bash, AskUserQuestion",true,"main","2a6d24be2ed571c5ff2319c506b60741bbcb1cb0","plugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fchangelog",483,"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-13 02:16:32",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":38},[51,54,57],{"tool":52,"command":53},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill changelog",{"tool":55,"command":56},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill changelog",{"tool":58,"command":59},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill changelog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fchangelog\u002FSKILL.md",[62,68],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Frelease.md","REFERENCE","参考文档",1445,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fchangelog\u002Freferences\u002Frelease.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fwriting-guidelines.md",1515,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freidemeister94\u002Fdevelopment-skills\u002Fskills\u002Fchangelog\u002Freferences\u002Fwriting-guidelines.md",[73,81,88,95,122,147],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":80},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":80},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":32},"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",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":32},"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",[],[129,130,131,117,132,133,134,135,136,137,138,139,140,141,107,142,143,144,145,146],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":164,"publishedAt":32},"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",[153,158,161],{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":159,"categoryName":160,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":162,"categoryName":163,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000010","后端与接口",[149,165,166,167,168,169,170,143,171,108,172,173,174,175,113,176,177,178,179,180],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]