AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Developer Artifact Shaper

skill-45ck-skill-harness-developer-artifact-shaper · by 45ck

Choose the right developer artifact type, source of truth, and review surface for a task.

↗ Website ↗ Repository
— No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-45ck-skill-harness-developer-artifact-shaper

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Developer Artifact Shaper? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Developer Artifact Shaper

Use this skill when a task needs a plan, design note, investigation, review report, or handoff artifact.

Core Rule

Pick the artifact format from the job it must do:

  • Markdown or TOON for canonical source, git diffs, CLI/TUI handoff, and long-lived docs.
  • HTML for generated human review surfaces, dense comparisons, visual diagrams, prototypes, dashboards, or desktop app previews.
  • Dual when a durable source and a rich review surface are both useful.
  • Model review artifacts use durable text sources and generated static review views; do not make rendered diagrams the only source.
  • Product, business, data, research, UX, and mockup artifacts use visual-source-first pairs when humans need visual inspection: agent-readable source plus generated visual review surface.
  • High-fidelity is the default for UI, customer-facing workflow, product, and mockup review. Low-fidelity sketches are scratch only unless explicitly captured as evidence.

Do not make generated HTML the only durable source for a decision.

Process

  1. Identify the artifact purpose: decision, plan, investigation, review, report, runbook, product brief, business case, data definition, research synthesis, UX flow, handoff, or prototype.
  2. Identify the canonical source location.
  3. Decide the review surface: markdown, html, or dual.
  4. Name the evidence that must be linked.
  5. For visual artifacts, choose the family: product, business, data, research, or UX.
  6. Decide whether the artifact should be listed in docs/artifacts/artifacts.manifest.json.
  7. State the update rule: edit source first, regenerate review surface second.

Output

Artifact Type

Canonical Source

Review Surface

Artifact Family

Evidence Links

Manifest Entry

Update Rule

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

  • Author: 45ck
  • Source: 45ck/skill-harness
  • License: MIT
  • Homepage: https://github.com/45ck/skill-harness/releases/tag/v0.1.0

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills