Update to Claus Argos Skill OS
Snapshot Nov 21, 2026 · 00:11 UTC · version 1.16.1
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for create-professional-documents
Skill instructions — Now says: technical specification package, have the responsible technical specialists establish requirements, architecture and readiness. This skill may organize,...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Sep 30, 2026 · 23:14 UTC
multi-document developer specification package, route architecture, authority, precedence, and readiness to `$architect-implementation-documentation`. This skill may render or format approved source content, but must establish content
Nov 21, 2026 · 00:11 UTC
technical specification package, have the responsible technical specialists establish requirements, architecture and readiness. This skill may organize, render or format the approved content; establish its
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -12,6 +12,6 @@ ## Implementation-package boundary -For a complex multi-document developer specification package, route architecture, authority, precedence, and readiness to `$architect-implementation-documentation`. This skill may render or format approved source content, but must establish content structure and correctness before layout work. +For a complex technical specification package, have the responsible technical specialists establish requirements, architecture and readiness. This skill may organize, render or format the approved content; establish its structure and correctness before layout work. Carry artifact ID, version, status, owner, date, sources, usage class, relationships, and downstream dependencies into controlled outputs. A clean, premium, or complete-looking document is not thereby `FINAL` or implementation-ready.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: create-professional-documents\ndescription: Plan and create polished professional documents and artifact suites such as strategy papers, business plans, proposals, reports, briefs, SOPs, presentations, spreadsheets, and decision memos. Use when the user needs a complete business artifact and the correct file-specific skill should be selected and coordinated.\n---\n# Create Professional Documents\n1. Define document purpose, audience, decision, format, language, brand, source material, constraints, and acceptance criteria.\n2. Select the correct artifact and invoke available document, presentation, spreadsheet, or PDF skills when producing those file types.\n3. Build an evidence-backed outline and assign each section a communication job.\n4. Draft with consistent terminology, hierarchy, tables/visuals only when helpful, citations, and explicit assumptions.\n5. Verify factual accuracy, completeness, tone, accessibility, layout, links, and requested file behavior.\n6. Deliver final artifact, source/assumption note, and concise usage guidance. Do not claim a file was rendered or verified unless it was.\n\n## Implementation-package boundary\n\nFor a complex multi-document developer specification package, route architecture, authority, precedence, and readiness to `$architect-implementation-documentation`. This skill may render or format approved source content, but must establish content structure and correctness before layout work.\n\nCarry artifact ID, version, status, owner, date, sources, usage class, relationships, and downstream dependencies into controlled outputs. A clean, premium, or complete-looking document is not thereby `FINAL` or implementation-ready.\n"
"---\nname: create-professional-documents\ndescription: Plan and create polished professional documents and artifact suites such as strategy papers, business plans, proposals, reports, briefs, SOPs, presentations, spreadsheets, and decision memos. Use when the user needs a complete business artifact and the correct file-specific skill should be selected and coordinated.\n---\n# Create Professional Documents\n1. Define document purpose, audience, decision, format, language, brand, source material, constraints, and acceptance criteria.\n2. Select the correct artifact and invoke available document, presentation, spreadsheet, or PDF skills when producing those file types.\n3. Build an evidence-backed outline and assign each section a communication job.\n4. Draft with consistent terminology, hierarchy, tables/visuals only when helpful, citations, and explicit assumptions.\n5. Verify factual accuracy, completeness, tone, accessibility, layout, links, and requested file behavior.\n6. Deliver final artifact, source/assumption note, and concise usage guidance. Do not claim a file was rendered or verified unless it was.\n\n## Implementation-package boundary\n\nFor a complex technical specification package, have the responsible technical specialists establish requirements, architecture and readiness. This skill may organize, render or format the approved content; establish its structure and correctness before layout work.\n\nCarry artifact ID, version, status, owner, date, sources, usage class, relationships, and downstream dependencies into controlled outputs. A clean, premium, or complete-looking document is not thereby `FINAL` or implementation-ready.\n"
Full snapshot data
{
"description": "Plan and create polished professional documents and artifact suites such as strategy papers, business plans, proposals, reports, briefs, SOPs, presentations, spreadsheets, and decision memos. Use when the user needs a complete business artifact and the correct file-specific skill should be selected and coordinated.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 246
}
],
"name": "create-professional-documents",
"skill_md_contents": "---\nname: create-professional-documents\ndescription: Plan and create polished professional documents and artifact suites such as strategy papers, business plans, proposals, reports, briefs, SOPs, presentations, spreadsheets, and decision memos. Use when the user needs a complete business artifact and the correct file-specific skill should be selected and coordinated.\n---\n# Create Professional Documents\n1. Define document purpose, audience, decision, format, language, brand, source material, constraints, and acceptance criteria.\n2. Select the correct artifact and invoke available document, presentation, spreadsheet, or PDF skills when producing those file types.\n3. Build an evidence-backed outline and assign each section a communication job.\n4. Draft with consistent terminology, hierarchy, tables/visuals only when helpful, citations, and explicit assumptions.\n5. Verify factual accuracy, completeness, tone, accessibility, layout, links, and requested file behavior.\n6. Deliver final artifact, source/assumption note, and concise usage guidance. Do not claim a file was rendered or verified unless it was.\n\n## Implementation-package boundary\n\nFor a complex technical specification package, have the responsible technical specialists establish requirements, architecture and readiness. This skill may organize, render or format the approved content; establish its structure and correctness before layout work.\n\nCarry artifact ID, version, status, owner, date, sources, usage class, relationships, and downstream dependencies into controlled outputs. A clean, premium, or complete-looking document is not thereby `FINAL` or implementation-ready.\n"
}SHA-256 of public snapshot: 57619e3190ffee1bb27e19dbd8bf2d6a47f06f0e63724d38cf89a296134165de