[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJ4816J2WJNNCH7C1AFGQ2":3,"skill-same:01M6MJ4816J2WJNNCH7C1AFGQ2":80},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6MJ4816J2WJNNCH7C1AFGQ2","stss",null,"Reduce defensive disclaimers, stacked hedging, and self-protective narration when drafting, rewriting, or auditing proposals, articles, case studies, captions, and other reader-facing prose. Use when defensive wording is requested for review or appears in a draft, including wording the assistant adds. Preserve meaningful limits; do not perform general style cleanup or ordinary code work.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flennney\u002Fstop-that-shit\u002Fskills\u002Fstss\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"self","drafting","when","limits","preserve","reduce","for","defensive","case","style","draft","assistant","do","narration","general","use","proposals","work","Captions","code","cleanup","review","2026-11-10 10:12:30",false,"---\nname: stss\ndescription: Reduce defensive disclaimers, stacked hedging, and self-protective narration when drafting, rewriting, or auditing proposals, articles, case studies, captions, and other reader-facing prose. Use when defensive wording is requested for review or appears in a draft, including wording the assistant adds. Preserve meaningful limits; do not perform general style cleanup or ordinary code work.\nlicense: MIT\n---\n\n# Stop That Shit Slop\n\n别再废话。\n\nMake the point without writing for an imaginary critic. Preserve limitations that change what the reader understands or decides.\n\n## Stay in scope\n\nReduce defensive wording in reader-facing prose, including captions and introductions. Do not classify text as AI-written, promise to remove an \"AI voice,\" humanize unrelated prose, or perform a general style cleanup.\n\nJudge sentences by their reader use, including sentences introduced during drafting. A request to describe a project's evolution calls for that history; it does not by itself call for an account of how the article's sources were checked.\n\n## Select the mode\n\n- `rewrite`: Return a tighter version. This is the default when the user provides text without a mode.\n- `audit`: Identify defensive writing and propose the smallest useful fix. Do not rewrite the full text.\n\nFollow an explicit mode. Infer the mode from the request only when none is given.\n\nFor a drafting request, create the requested artifact from the supplied material and apply the rewrite checks before returning it.\n\n## Record the claims\n\nBefore editing, build a private Claim Ledger from the supplied material:\n\n- facts and numbers;\n- named actors and sources;\n- evidence strength;\n- stated uncertainty and scope;\n- what the reader needs to understand or do.\n\nDo not print the ledger unless the user asks for it. Do not add facts, sources, numbers, certainty, or causality.\n\nKeeping facts accurate does not require printing every editorial note. Keep verification logs and source-checking process in working notes unless the reader needs them. Preserve useful attribution, actual methods, and conditions that affect a claim.\n\n## Test each defensive sentence\n\nApply the Sentence Consumer Test:\n\n1. Who will use this sentence?\n2. What understanding or decision does it change for this reader?\n3. What becomes false or misleading if it is removed?\n\nChoose one action:\n\n- `DROP`: It only narrates diligence, anticipates criticism, apologizes, or says what the document does not attempt.\n- `CALIBRATE`: It contains real uncertainty but uses stacked hedges. Keep one precise limitation.\n- `RELOCATE`: The reader needs it beside a particular claim, or only the editor needs it in working notes. Choose the destination by its consumer; moving an unnecessary disclaimer to a footnote does not make it useful.\n- `KEEP`: It changes the meaning, evidence strength, attribution, or a legal, safety, financial, methodological, contractual, or scope decision.\n\nDo not decide from a keyword alone. The same phrase can be waste in one context and necessary in another.\n\n## Rewrite\n\n1. Lead with the requested subject, claim, decision, or proposal.\n2. State scope positively: say what the work covers.\n3. Replace stacked hedges with one evidence-matched qualifier.\n4. Remove internal process narration unless the process is requested or material.\n5. Put a necessary limitation beside the claim it limits.\n6. Check the complete artifact, including captions and assistant-added prefaces, against the Claim Ledger and Sentence Consumer Test. Do not reintroduce dropped defenses in the delivery note.\n\nReturn only the requested artifact unless the user asks for commentary. If the text is already direct and faithful, return it unchanged.\n\n## Audit\n\nReport only actionable findings. For each finding, give:\n\n- the span or sentence;\n- `DROP`, `CALIBRATE`, `RELOCATE`, or `KEEP`;\n- the reader's interpretation or decision affected;\n- the smallest replacement when one is needed.\n\nUse `NO_DECISION_CONSUMER` when a sentence serves neither reader understanding nor a decision. If there are no actionable findings, say so and stop.\n\n## Check the claim diff\n\nBefore returning the result, verify:\n\n- no supplied fact, number, source, or actor disappeared without reason;\n- no new fact, number, source, or actor appeared;\n- uncertainty did not become certainty;\n- correlation did not become causation;\n- a requested or meaning-changing limitation remains visible.\n\nRun one claim-preserving pass. Do not add a score, a probability that text is AI-written, a change diary, or repeated self-review.\n\nRead [references\u002Fexamples.md](references\u002Fexamples.md) when the boundary is ambiguous or the user asks for examples.\n","# Stop That Shit Slop\n\n别再废话。\n\nMake the point without writing for an imaginary critic. Preserve limitations that change what the reader understands or decides.\n\n## Stay in scope\n\nReduce defensive wording in reader-facing prose, including captions and introductions. Do not classify text as AI-written, promise to remove an \"AI voice,\" humanize unrelated prose, or perform a general style cleanup.\n\nJudge sentences by their reader use, including sentences introduced during drafting. A request to describe a project's evolution calls for that history; it does not by itself call for an account of how the article's sources were checked.\n\n## Select the mode\n\n- `rewrite`: Return a tighter version. This is the default when the user provides text without a mode.\n- `audit`: Identify defensive writing and propose the smallest useful fix. Do not rewrite the full text.\n\nFollow an explicit mode. Infer the mode from the request only when none is given.\n\nFor a drafting request, create the requested artifact from the supplied material and apply the rewrite checks before returning it.\n\n## Record the claims\n\nBefore editing, build a private Claim Ledger from the supplied material:\n\n- facts and numbers;\n- named actors and sources;\n- evidence strength;\n- stated uncertainty and scope;\n- what the reader needs to understand or do.\n\nDo not print the ledger unless the user asks for it. Do not add facts, sources, numbers, certainty, or causality.\n\nKeeping facts accurate does not require printing every editorial note. Keep verification logs and source-checking process in working notes unless the reader needs them. Preserve useful attribution, actual methods, and conditions that affect a claim.\n\n## Test each defensive sentence\n\nApply the Sentence Consumer Test:\n\n1. Who will use this sentence?\n2. What understanding or decision does it change for this reader?\n3. What becomes false or misleading if it is removed?\n\nChoose one action:\n\n- `DROP`: It only narrates diligence, anticipates criticism, apologizes, or says what the document does not attempt.\n- `CALIBRATE`: It contains real uncertainty but uses stacked hedges. Keep one precise limitation.\n- `RELOCATE`: The reader needs it beside a particular claim, or only the editor needs it in working notes. Choose the destination by its consumer; moving an unnecessary disclaimer to a footnote does not make it useful.\n- `KEEP`: It changes the meaning, evidence strength, attribution, or a legal, safety, financial, methodological, contractual, or scope decision.\n\nDo not decide from a keyword alone. The same phrase can be waste in one context and necessary in another.\n\n## Rewrite\n\n1. Lead with the requested subject, claim, decision, or proposal.\n2. State scope positively: say what the work covers.\n3. Replace stacked hedges with one evidence-matched qualifier.\n4. Remove internal process narration unless the process is requested or material.\n5. Put a necessary limitation beside the claim it limits.\n6. Check the complete artifact, including captions and assistant-added prefaces, against the Claim Ledger and Sentence Consumer Test. Do not reintroduce dropped defenses in the delivery note.\n\nReturn only the requested artifact unless the user asks for commentary. If the text is already direct and faithful, return it unchanged.\n\n## Audit\n\nReport only actionable findings. For each finding, give:\n\n- the span or sentence;\n- `DROP`, `CALIBRATE`, `RELOCATE`, or `KEEP`;\n- the reader's interpretation or decision affected;\n- the smallest replacement when one is needed.\n\nUse `NO_DECISION_CONSUMER` when a sentence serves neither reader understanding nor a decision. If there are no actionable findings, say so and stop.\n\n## Check the claim diff\n\nBefore returning the result, verify:\n\n- no supplied fact, number, source, or actor disappeared without reason;\n- no new fact, number, source, or actor appeared;\n- uncertainty did not become certainty;\n- correlation did not become causation;\n- a requested or meaning-changing limitation remains visible.\n\nRun one claim-preserving pass. Do not add a score, a probability that text is AI-written, a change diary, or repeated self-review.\n\nRead [references\u002Fexamples.md](references\u002Fexamples.md) when the boundary is ambiguous or the user asks for examples.\n",{"name":5,"license":15,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Flennney\u002Fstop-that-shit\u002Fskills\u002Fstss",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill stss",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill stss",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill stss","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flennney\u002Fstop-that-shit\u002Fskills\u002Fstss\u002FSKILL.md",true,[70,76],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fopenai.yaml","REFERENCE","参考文档",311,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flennney\u002Fstop-that-shit\u002Fskills\u002Fstss\u002Fagents\u002Fopenai.yaml",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fexamples.md",7597,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flennney\u002Fstop-that-shit\u002Fskills\u002Fstss\u002Freferences\u002Fexamples.md",[81,90,98,106,114,122],{"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":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"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.","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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":89},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":89},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":89},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":89},"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":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":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":89},"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",[],[]]