| name | artifact-generation |
| description | Use when creating polished deliverables such as reports, docs, decks, spreadsheets, diagrams, templates, or packaged handoff artifacts from source material and task requirements. |
| version | 1.0.0 |
| triggers | ["create an artifact","generate a report","build a deliverable","package this handoff"] |
| negative_triggers | ["debug a runtime failure","only answer a factual question"] |
| allowed_tools | [] |
| required_tools | [] |
| trust_level | local |
| safety_class | standard |
| examples | ["Create a polished report, deck outline, spreadsheet, diagram, template, or handoff package from provided material."] |
| tests | ["sb skills validate --path skills --strict"] |
| performance | {"notes":"Best when source material, target audience, and output format are known."} |
Artifact Generation
Purpose
Produce useful deliverables from gathered context, with structure and polish
appropriate to the audience.
Instructions
- Confirm the artifact type, audience, source material, and success criteria from the request.
- Choose the simplest durable format that satisfies the task.
- Preserve citations, assumptions, and provenance when the artifact makes factual claims.
- Use consistent headings, tables, diagrams, or sections to make the artifact easy to scan.
- Validate the output format when a renderer, linter, or parser is available.
- End with the artifact location and verification result.
Quality Bar
- The artifact is complete enough to use immediately.
- Claims are grounded in provided or inspected sources.
- Formatting is deliberate and consistent.
- Open questions are explicit rather than hidden.
