[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCZQCBBE2AH29TQS2YY6V2":3,"skill-same:01M6MCZQCBBE2AH29TQS2YY6V2":69},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6MCZQCBBE2AH29TQS2YY6V2","unslop-commit",null,"Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI\u002Fmarketing slop (\"comprehensive solution\", \"robust implementation\", \"leverage\", \"enhance\", \"seamlessly\", \"This commit...\"). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when \"why\" isn't obvious from the subject. Use when user says \"humanize commit\", \"de-slop commit message\", \"make this commit sound human\", \"\u002Funslop-commit\", \"\u002Fcommit\", \"write a commit\", or pastes a draft commit to clean up. Auto-triggers when staging changes.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMohamedAbdallah-14\u002Funslop\u002Fskills\u002Funslop-commit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"unslop","unslop commit","commit","conventional commits","when","slop","draft commit","de","leverage","human","message","humanize","clean","engineer","up","only","auto","write","marketing","why","messages","2026-11-10 10:12:30",false,"---\nname: unslop-commit\ndescription: >\n  Rewrites commit messages so they sound like a careful human engineer wrote them.\n  Strips AI\u002Fmarketing slop (\"comprehensive solution\", \"robust implementation\", \"leverage\", \"enhance\",\n  \"seamlessly\", \"This commit...\"). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50),\n  imperative mood. Body only when \"why\" isn't obvious from the subject.\n  Use when user says \"humanize commit\", \"de-slop commit message\", \"make this commit sound human\",\n  \"\u002Funslop-commit\", \"\u002Fcommit\", \"write a commit\", or pastes a draft commit to clean up.\n  Auto-triggers when staging changes.\n---\n\n# Unslop Commit\n\n## Purpose\n\nGenerate or rewrite commit messages so they read like a real engineer wrote them at the end of a real day. Conventional Commits format. Direct, specific, no template English. Why over what.\n\n## Trigger\n\n`\u002Funslop-commit`, `\u002Fcommit`, \"write a commit\", \"commit message\", \"humanize this commit\", \"de-slop this commit\". Auto-trigger when the user has staged changes and asks for a commit message.\n\n## Rules\n\n### Subject line\n\n- Format: `\u003Ctype>(\u003Cscope>): \u003Cimperative summary>`\n- Scope optional. Types: `feat`, `fix`, `chore`, `refactor`, `docs`, `test`, `perf`, `build`, `ci`, `revert`.\n- Imperative mood: `add`, `fix`, `move`, `remove` — not `added`, `fixes`, `fixing`.\n- ≤50 chars when possible. Hard cap 72.\n- No trailing period.\n- Lowercase after `:` unless the project capitalizes.\n\n### Body (only when subject can't carry it)\n\n- Add for: non-obvious \"why\", breaking changes, migrations, security context, data integrity.\n- Wrap at 72 chars. Bullets `-` for two or more independent points. Single paragraph for one thought.\n- End with refs: `Closes #42`, `Refs #17`. No `BREAKING CHANGE:` unless truly breaking — and then write it.\n\n### Never include\n\n- Template prefixes: \"This commit...\", \"This change...\", \"We are...\", \"I have...\"\n- Marketing verbs: comprehensive, robust, enhance, leverage, seamless, holistic\n- Filler adverbs: just, really, basically, simply, actually\n- Restating the filename when scope already names it\n- \"As requested by...\" (use `Co-authored-by:` if you need attribution)\n- AI attribution unless the project requires it\n- Emoji unless project convention says so\n\n### Auto-clarity (always include body)\n\n- Breaking changes\n- Security fixes\n- Data migrations\n- Reverts (cite the reverted commit)\n\n## Examples\n\n### Bad → good (slop subject, no body)\n\n- Bad: `feat: implement a comprehensive, robust solution for user profile retrieval with enhanced error handling`\n- Good: `feat(api): return profile fields the mobile client actually needs`\n\n### Bad → good (vague body)\n\nBad:\n```\nfix: fixed the bug\n\nThis commit addresses an issue where the application was not working correctly\nin some edge cases. We've improved the logic to handle these scenarios.\n```\n\nGood:\n```\nfix(checkout): ignore stale cart id from localStorage\n\nStale cart ids came from tabs that hadn't refreshed after a deploy. Server\nnow treats unknown ids as empty cart instead of 500.\n\nCloses #842\n```\n\n### Breaking change\n\n```\nfeat(api)!: rename \u002Fv1\u002Forders to \u002Fv1\u002Fcustomer-orders\n\nThe old route stays in place until the next major release but logs a\ndeprecation warning. Internal services have been migrated.\n\nBREAKING CHANGE: third-party integrations using \u002Fv1\u002Forders directly need\nto switch to \u002Fv1\u002Fcustomer-orders by 2026-07-01.\n\nCloses #1290\n```\n\n## Boundaries\n\n- Output the message only, in a single fenced block, ready to paste.\n- Do not run `git commit`, stage, or amend.\n- If the change is genuinely trivial (`docs(readme): fix typo`), keep it trivial. Don't pad.\n- Never invent context the user didn't provide. If the \"why\" isn't clear, ask, or omit the body.\n","# Unslop Commit\n\n## Purpose\n\nGenerate or rewrite commit messages so they read like a real engineer wrote them at the end of a real day. Conventional Commits format. Direct, specific, no template English. Why over what.\n\n## Trigger\n\n`\u002Funslop-commit`, `\u002Fcommit`, \"write a commit\", \"commit message\", \"humanize this commit\", \"de-slop this commit\". Auto-trigger when the user has staged changes and asks for a commit message.\n\n## Rules\n\n### Subject line\n\n- Format: `\u003Ctype>(\u003Cscope>): \u003Cimperative summary>`\n- Scope optional. Types: `feat`, `fix`, `chore`, `refactor`, `docs`, `test`, `perf`, `build`, `ci`, `revert`.\n- Imperative mood: `add`, `fix`, `move`, `remove` — not `added`, `fixes`, `fixing`.\n- ≤50 chars when possible. Hard cap 72.\n- No trailing period.\n- Lowercase after `:` unless the project capitalizes.\n\n### Body (only when subject can't carry it)\n\n- Add for: non-obvious \"why\", breaking changes, migrations, security context, data integrity.\n- Wrap at 72 chars. Bullets `-` for two or more independent points. Single paragraph for one thought.\n- End with refs: `Closes #42`, `Refs #17`. No `BREAKING CHANGE:` unless truly breaking — and then write it.\n\n### Never include\n\n- Template prefixes: \"This commit...\", \"This change...\", \"We are...\", \"I have...\"\n- Marketing verbs: comprehensive, robust, enhance, leverage, seamless, holistic\n- Filler adverbs: just, really, basically, simply, actually\n- Restating the filename when scope already names it\n- \"As requested by...\" (use `Co-authored-by:` if you need attribution)\n- AI attribution unless the project requires it\n- Emoji unless project convention says so\n\n### Auto-clarity (always include body)\n\n- Breaking changes\n- Security fixes\n- Data migrations\n- Reverts (cite the reverted commit)\n\n## Examples\n\n### Bad → good (slop subject, no body)\n\n- Bad: `feat: implement a comprehensive, robust solution for user profile retrieval with enhanced error handling`\n- Good: `feat(api): return profile fields the mobile client actually needs`\n\n### Bad → good (vague body)\n\nBad:\n```\nfix: fixed the bug\n\nThis commit addresses an issue where the application was not working correctly\nin some edge cases. We've improved the logic to handle these scenarios.\n```\n\nGood:\n```\nfix(checkout): ignore stale cart id from localStorage\n\nStale cart ids came from tabs that hadn't refreshed after a deploy. Server\nnow treats unknown ids as empty cart instead of 500.\n\nCloses #842\n```\n\n### Breaking change\n\n```\nfeat(api)!: rename \u002Fv1\u002Forders to \u002Fv1\u002Fcustomer-orders\n\nThe old route stays in place until the next major release but logs a\ndeprecation warning. Internal services have been migrated.\n\nBREAKING CHANGE: third-party integrations using \u002Fv1\u002Forders directly need\nto switch to \u002Fv1\u002Fcustomer-orders by 2026-07-01.\n\nCloses #1290\n```\n\n## Boundaries\n\n- Output the message only, in a single fenced block, ready to paste.\n- Do not run `git commit`, stage, or amend.\n- If the change is genuinely trivial (`docs(readme): fix typo`), keep it trivial. Don't pad.\n- Never invent context the user didn't provide. If the \"why\" isn't clear, ask, or omit the body.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FMohamedAbdallah-14\u002Funslop\u002Fskills\u002Funslop-commit",491,"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-14 14:06:13",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill unslop-commit",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill unslop-commit",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill unslop-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMohamedAbdallah-14\u002Funslop\u002Fskills\u002Funslop-commit\u002FSKILL.md",true,[],[70,80,88,96,104,112],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\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":74,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":79},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]