Skill Issue
Trigger
Apply this library standard when authoring, reviewing, naming, or deciding admission for an agent skill.
Scope
This SOP governs skill form in this library; skill-creator owns evaluation, iteration, and description optimization.
Existing skills predate this standard and stay unchanged unless the client explicitly places them in scope.
Inputs
The form decision accepts the proposed skill's purpose and candidate content; evaluation evidence belongs to skill-creator.
Roles
The authoring agent applies this standard; the client decides admission disputes and taste calls.
Procedure
- Reject the skill unless its candidate content contains at least one survivor category in the litmus.
- Classify the admitted skill as exactly one of the five types in the typology.
- Name the skill by its type's rule.
- Write all nine sections in this order: Trigger, Scope, Inputs, Roles, Procedure, Outputs, Exceptions, QC, References; write
None. in an inapplicable section.
- Reduce the skill to: “When [trigger] occurs, [role] performs [procedure] using [inputs] to produce [output], while satisfying [controls].”
- Delete every body line an agent with perfect reasoning and perfect public-world knowledge could derive.
- Move bulky non-derivable material to
references/, deterministic operations to scripts/, and write the frontmatter description by the description canon.
Outputs
Record compliance as one conforming skill directory containing SKILL.md and only required attachments; this Policy SOP produces no domain work product.
Exceptions
A failed admission gate yields a rejection, not a thinner skill.
Escalate admission disputes to the client; never waive the gate silently.
QC
- Confirm a survivor category earned admission and every retained body line passes the litmus.
- Confirm the type is singular, the name follows its type, and all nine ordered sections are present.
- Confirm the name matches its directory, uses lowercase hyphens, and is at most 64 characters.
- Confirm the body is under 500 lines and 5,000 tokens; each reference over 100 lines has a table of contents.
- Confirm the non-empty third-person description is at most 1,024 characters, contains no XML, and states positive and negative triggers.
- Confirm the trigger-eval optimizer's final description is applied verbatim.
References
Read SOP types for classification or naming, the litmus for admission or line review, and the description canon when writing frontmatter.
1---2name: skill-issue3description: Triggers when an agent authors, reviews, names, or decides whether to create an agent skill, including requests to write SKILL.md, choose a skill type, evaluate skill-worthy content, or split material into references/scripts. Not for running skill evaluations or description optimization, which belong to skill-creator.4---56# Skill Issue78## Trigger910Apply this library standard when authoring, reviewing, naming, or deciding admission for an agent skill.1112## Scope1314This SOP governs skill form in this library; `skill-creator` owns evaluation, iteration, and description optimization.15Existing skills predate this standard and stay unchanged unless the client explicitly places them in scope.1617## Inputs1819The form decision accepts the proposed skill's purpose and candidate content; evaluation evidence belongs to `skill-creator`.2021## Roles2223The authoring agent applies this standard; the client decides admission disputes and taste calls.2425## Procedure26271. Reject the skill unless its candidate content contains at least one survivor category in [the litmus](references/litmus.md).282. Classify the admitted skill as exactly one of the five types in [the typology](references/sop-types.md).293. Name the skill by its type's rule.304. Write all nine sections in this order: Trigger, Scope, Inputs, Roles, Procedure, Outputs, Exceptions, QC, References; write `None.` in an inapplicable section.315. Reduce the skill to: “When [trigger] occurs, [role] performs [procedure] using [inputs] to produce [output], while satisfying [controls].”326. Delete every body line an agent with perfect reasoning and perfect public-world knowledge could derive.337. Move bulky non-derivable material to `references/`, deterministic operations to `scripts/`, and write the frontmatter description by [the description canon](references/description-canon.md).3435## Outputs3637Record compliance as one conforming skill directory containing `SKILL.md` and only required attachments; this Policy SOP produces no domain work product.3839## Exceptions4041A failed admission gate yields a rejection, not a thinner skill.42Escalate admission disputes to the client; never waive the gate silently.4344## QC4546- Confirm a survivor category earned admission and every retained body line passes the litmus.47- Confirm the type is singular, the name follows its type, and all nine ordered sections are present.48- Confirm the name matches its directory, uses lowercase hyphens, and is at most 64 characters.49- Confirm the body is under 500 lines and 5,000 tokens; each reference over 100 lines has a table of contents.50- Confirm the non-empty third-person description is at most 1,024 characters, contains no XML, and states positive and negative triggers.51- Confirm the trigger-eval optimizer's final description is applied verbatim.5253## References5455Read [SOP types](references/sop-types.md) for classification or naming, [the litmus](references/litmus.md) for admission or line review, and [the description canon](references/description-canon.md) when writing frontmatter.
eliasstravik