[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79HA9EBVT8QSYDQ927BEXKQ":3,"skill-same:01M79HA9EBVT8QSYDQ927BEXKQ":51},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79HA9EBVT8QSYDQ927BEXKQ","guardrail-house-tone",null,"Outward text loads every writing skill it triggers before drafting, and ships only after the voice linter has run on it as a file and its exit is pasted. Use when the advocate role is composed.","coilyco\u002Fagent-compose","coilyco","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288480294?v=4","01M79H9204G28Z0FSRDTX8TK4K","01M79H920QW4TRWT86MKFXQ60R",1,"MIT","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Fseed\u002Froster\u002Fdata\u002Fguardrail-house-tone\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: guardrail-house-tone\ndescription: Outward text loads every writing skill it triggers before drafting, and ships only after the voice linter has run on it as a file and its exit is pasted. Use when the advocate role is composed.\n---\n\n# Guardrail: house tone\n\nOutward text does not ship until the linter has run on it as a file and you have pasted its exit. Text composed in a message and never written to disk was never linted, and sending it is the violation this guardrail exists to catch. Clear every house-style hit before sending, then hand-check the two things a regex cannot reach.\n\n## The procedure\n\nWrite it to a file. The linter takes a path, so outward prose drafted in\na chat message and sent from there bypasses the detector completely. That\nis the only way this guardrail actually fails.\n\nRun it. The deployment names the linter and the profile it carries, so\nresolve both from this seat's own configuration rather than assuming a\npath. Paste the violation lines and the exit status beside the draft. A\nsilent clean run is reported as a clean run rather than as silence.\n\nEvery rule carries a level. An L2 or L3 hit refuses this seat's reply, so clear\nevery one of those. An L1 hit warns and does not refuse, and it still gets\nthe treatment below.\n\nThe two halves of a hit. A profile carries house-style rules, which are\nthis deployment's own settled decisions about punctuation, emphasis,\npronouns and address. Those are not negotiable and you clear every one.\nSome of them over-flag by design, and those clear by reading the referent\nand confirming the rule does not apply rather than by editing. The rest of\na profile is slop vocabulary compiled from external sources, where a hit\nis an instruction to reread the sentence rather than to rewrite it, and\noverriding one is fine when you say which and why.\n\nName a rule by its effect rather than by its id. Quoting an id in prose\ntrips the rule it names, which is how the first draft of this text failed\nits own check.\n\nWhat the regex cannot reach, and you must: no people's names in public\nartifacts, which needs context the linter does not have.\n\nWhat does not count: a clean run on an earlier draft, a clean run on a\ndifferent file, and the linter's silence when you never gave it a path.\n\n## Load the writing skills before you draft, not after\n\nThe linter is a detector, and a detector catches only what a regex reaches.\nRegister, length band, and whether a constraint you name traces to something\nthe principal actually said are all invisible to it, and all three are how a\ndraft goes wrong.\n\nSo before drafting anything the comms boundary calls outward, load every\nwriting skill the task triggers and read the references each one names. The\ndeployment names those skills, so resolve them from this seat's catalog the way\nyou resolve the linter. A subject carrying its own doctrine loads that too,\nbecause what such an entry exists to catch reaches a reader through drafted\ntext more often than through a decision.\n\nA clean run on a draft written without them is a clean run on the wrong\nquestion, which is how a reply once cleared this guardrail at three times its\nregister's length while naming a constraint with no source behind it.\n","# Guardrail: house tone\n\nOutward text does not ship until the linter has run on it as a file and you have pasted its exit. Text composed in a message and never written to disk was never linted, and sending it is the violation this guardrail exists to catch. Clear every house-style hit before sending, then hand-check the two things a regex cannot reach.\n\n## The procedure\n\nWrite it to a file. The linter takes a path, so outward prose drafted in\na chat message and sent from there bypasses the detector completely. That\nis the only way this guardrail actually fails.\n\nRun it. The deployment names the linter and the profile it carries, so\nresolve both from this seat's own configuration rather than assuming a\npath. Paste the violation lines and the exit status beside the draft. A\nsilent clean run is reported as a clean run rather than as silence.\n\nEvery rule carries a level. An L2 or L3 hit refuses this seat's reply, so clear\nevery one of those. An L1 hit warns and does not refuse, and it still gets\nthe treatment below.\n\nThe two halves of a hit. A profile carries house-style rules, which are\nthis deployment's own settled decisions about punctuation, emphasis,\npronouns and address. Those are not negotiable and you clear every one.\nSome of them over-flag by design, and those clear by reading the referent\nand confirming the rule does not apply rather than by editing. The rest of\na profile is slop vocabulary compiled from external sources, where a hit\nis an instruction to reread the sentence rather than to rewrite it, and\noverriding one is fine when you say which and why.\n\nName a rule by its effect rather than by its id. Quoting an id in prose\ntrips the rule it names, which is how the first draft of this text failed\nits own check.\n\nWhat the regex cannot reach, and you must: no people's names in public\nartifacts, which needs context the linter does not have.\n\nWhat does not count: a clean run on an earlier draft, a clean run on a\ndifferent file, and the linter's silence when you never gave it a path.\n\n## Load the writing skills before you draft, not after\n\nThe linter is a detector, and a detector catches only what a regex reaches.\nRegister, length band, and whether a constraint you name traces to something\nthe principal actually said are all invisible to it, and all three are how a\ndraft goes wrong.\n\nSo before drafting anything the comms boundary calls outward, load every\nwriting skill the task triggers and read the references each one names. The\ndeployment names those skills, so resolve them from this seat's catalog the way\nyou resolve the linter. A subject carrying its own doctrine loads that too,\nbecause what such an entry exists to catch reaches a reader through drafted\ntext more often than through a decision.\n\nA clean run on a draft written without them is a clean run on the wrong\nquestion, which is how a reply once cleared this guardrail at three times its\nregister's length while naming a constraint with no source behind it.\n",{"name":5,"description":7},"main","d0a6ac0e6f6a57fcf95ee661a8644fa210af488f","seed\u002Froster\u002Fdata\u002Fguardrail-house-tone",0,"https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose","https:\u002F\u002Fgithub.com\u002Fcoilyco","https:\u002F\u002Fcoilyco.ai\u002F","2026-11-10 04:44:56",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add coilyco\u002Fagent-compose --skill guardrail-house-tone",{"tool":37,"command":38},"bunx","bunx skills add coilyco\u002Fagent-compose --skill guardrail-house-tone",{"tool":40,"command":41},"pnpm","pnpm dlx skills add coilyco\u002Fagent-compose --skill guardrail-house-tone","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Fseed\u002Froster\u002Fdata\u002Fguardrail-house-tone\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"guardrail.yaml","REFERENCE","参考文档",548,"https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Fseed\u002Froster\u002Fdata\u002Fguardrail-house-tone\u002Fguardrail.yaml",[52,59,66,73,79,86],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M79HE38NZK3NCDR7BFQB74CE","role-courier","Fixture role. Carries one parcel from one place to one other place, and reports what happened to it.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fhandmade-bundle\u002Fcontent\u002Fskills\u002Ffixture%3Ahandmade\u002Frole-courier\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M79HE1F3KRM9QRVTPXZQ3QJX","personality-steady","Fixture personality. Keeps one pace regardless of what the surroundings are doing.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fhandmade-bundle\u002Fcontent\u002Fskills\u002Ffixture%3Ahandmade\u002Fpersonality-steady\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M79HDYSWCR6AXMH2J0B08X9N","fixture-review","Public fixture for native-skill and compiled-context contract tests.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fcontracts\u002Fskills\u002Ffixture-review\u002FSKILL.md",[],[],{"skillNo":74,"name":61,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M79HDW1NC2P1G6TMZ3FBTTXB","Bring calm follow-through and stability to workbench tasks.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fcontracts\u002Fperson-independent\u002Fdefinitions\u002Fskills\u002Fpersonality-steady\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M79HDS77RSJC9WE36EXX571Q","personality-bright","Bring clarity and constructive energy to workbench tasks.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Ftestdata\u002Fcontracts\u002Fperson-independent\u002Fdefinitions\u002Fskills\u002Fpersonality-bright\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M79HDNQ7YM56A4F37M6FCRYC","role-sysadmin-senior","Adopt the Senior Sysadmin charter for controlled running-system changes, executed by your own hand. Use when the session assigns, infers, or explicitly switches to the senior-sysadmin role.","https:\u002F\u002Fgithub.com\u002Fcoilyco\u002Fagent-compose\u002Fblob\u002Fmain\u002Fseed\u002Froster\u002Fdata\u002Frole-sysadmin-senior\u002FSKILL.md",[],[]]