Artifact packager

Skill arniesaha/ctxops/skills/artifact-packager

WHEN shaping a one-off durable shareable artifact. Triggers: blog post, README, case study, teardown, vision doc, design doc summary, launch page, demo script, internal whitepaper, 'write the v1 of X', 'turn this thread into a doc'. OUTPUT: draft artifact in target format plus a publish checklist. PAIR BEFORE: ctx-pack (ground the artifact in real work). NOT FOR: recurring progress messages (use status-update). If you'd send a fresh version next week, that's status-update territory.From its SKILL.md

Install

npx -y skills add arniesaha/ctxops --skill artifact-packager

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 276 tokens by cl100k_base, as published. Nobody here has run it

artifact-packager

One-off durable artifacts. Different from status-update (recurring progress). The heuristic is recurrence: would you send another version with new content next week? If yes, use status-update.

Artifact Types

Blog post
LinkedIn post
GitHub README
Product landing copy
Teardown page
Case study
Demo script
Launch checklist
Change explainer + comprehension quiz (post-implementation: what changed and why, bundled with spec and implementation notes, ending with a short quiz that checks the reader actually absorbed it)
Internal-facing: Linear update, Slack announcement, weekly note, design doc summary

For internal artifacts, use status-update instead when the goal is recurring progress reporting. Use this skill when shaping a one-off durable artifact.

Workflow

Identify the audience and the artifact type.
Extract source material from real work, not generic claims.
Choose the thesis or narrative spine.
Draft the artifact in the target format.
Remove private details, sensitive paths, credentials, names, and unnecessary brand references.
Add a short publish checklist.

Rules

Preserve concrete technical detail where it proves the point.
Remove chatty session residue.
Do not invent proof.
Mark placeholders clearly.
Ask before publishing externally.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.