[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FCRQNEYW641WZC6AFSFF0E":3,"skill-same:01M6FCRQNEYW641WZC6AFSFF0E":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":29,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6FCRQNEYW641WZC6AFSFF0E","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.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-unslop-commit\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"commit","unslop","unslop commit","2026","github","blob","slop","tree","critical","leverage","human","main","community","conventional commits","implementation","enhance","engineer","format","commits","careful","messages","plugins","https","license","2026-11-10 10:12:30",false,"---\nname: unslop-commit\ndescription: \"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.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FMohamedAbdallah-14\u002Funslop\u002Ftree\u002Fmain\u002Fplugins\u002Funslop\u002Fskills\u002Funslop-commit\nsource_repo: MohamedAbdallah-14\u002Funslop\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FMohamedAbdallah-14\u002Funslop\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Unslop Commit\n## When to Use\n\nUse when drafting or rewriting a commit message from the actual diff and supplied context. Keep Conventional Commits format and a subject no longer than 72 characters (aim for 50).\n\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...\" filler; preserve required attribution. Use `Co-authored-by:` only for an actual co-author with the correct identity, not merely a requester.\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 is removed in this release. Internal services have been\nmigrated to \u002Fv1\u002Fcustomer-orders.\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\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Unslop Commit\n## When to Use\n\nUse when drafting or rewriting a commit message from the actual diff and supplied context. Keep Conventional Commits format and a subject no longer than 72 characters (aim for 50).\n\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...\" filler; preserve required attribution. Use `Co-authored-by:` only for an actual co-author with the correct identity, not merely a requester.\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 is removed in this release. Internal services have been\nmigrated to \u002Fv1\u002Fcustomer-orders.\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\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":26,"source":47,"license":14,"date_added":48,"description":7,"source_repo":49,"source_type":30,"license_source":50},"https:\u002F\u002Fgithub.com\u002FMohamedAbdallah-14\u002Funslop\u002Ftree\u002Fmain\u002Fplugins\u002Funslop\u002Fskills\u002Funslop-commit",1782864000000,"MohamedAbdallah-14\u002Funslop","https:\u002F\u002Fgithub.com\u002FMohamedAbdallah-14\u002Funslop\u002Fblob\u002Fmain\u002FLICENSE","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-unslop-commit",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-12 14:21:24",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add boisenoise\u002Fskills-collections --skill unslop-commit",{"tool":63,"command":64},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill unslop-commit",{"tool":66,"command":67},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill unslop-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-unslop-commit\u002FSKILL.md",true,[],[72,100,125,150,169,192],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":42},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,26,96,97,98,99,21],"web","access","web access","official","development","browser","search","data","Tools","read","fetch","only","youtube","free tools","platform","free","cover","normal","when",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":112,"publishedAt":42},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[107],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[102,113,114,22,84,85,41,89,115,116,117,118,119,120,121,26,122,123,124,23,21],"MCP","cli","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":137,"publishedAt":42},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[127,22,84,41,40,138,139,140,141,142,26,143,144,145,123,146,147,148,149,23,102,21],"email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":42},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[158,159,160,22,84,41,161,162,40,163,115,164,165,166,141,26,167,168,23,102,21],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":173,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":42},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[177,178,22,179,84,180,41,181,182,183,184,185,26,186,187,188,189,190,191,23],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":42},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[200,201,202,22,84,41,203,204,140,205,206,26,207,208,209,210,211,212,213,23],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]