CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-artifact

Generate and publish a project status artifact — an opinionated, tabbed status page for a project too big for one update (overview & success criteria, the workstream sequence, next steps, plus background, plan, risks & open questions, and decisions/FAQ when they earn a tab) — published with the built-in Artifact tool to a default-private claude.ai page the user can share with teammates. Use when a piece of work spans several workstreams and you want a shareable overview kept current. Each artifact is backed by a small per-project config in the plugin data dir, so refreshing it re-gathers live state, redeploys the same URL, and reports only the delta. For software projects whose workstreams are PRs, also read swe.md (the X.Y PR-numbering convention; pulling PR state with gh/git; a per-PR detail block). Needs the built-in Artifact tool (claude.ai login). Not for single-PR changes or public docs.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/project-artifact/skills/project-artifact/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The workflow is a model of explicit sequencing with genuine validation and recovery loops, and the in-file guidance is specific down to paths and tool parameters. It is dragged down by the two referenced bundle files (template.html, swe.md) being missing — the workflow's most executable assets — and by a body length that includes recurring justificatory padding.

Suggestions

Ship the referenced bundle files (template.html and swe.md) in the skill directory, or remove the references and inline the minimal required content (the state-block field list, a minimal tab skeleton) so steps 3 and the refresh section are self-sufficient.

Trim justificatory asides (the SVG benefits list, the hub/slug rationale, the coffee-chat framing) to their operative instruction — roughly: 'diagrams are inline SVG, not images; skip the dependency DAG; the slug is opaque so register on the hub if one exists'.

Tighten the multi-clause sentences in the tab catalog and Conventions sections into short normative statements, moving the 'why' to a single line per rule at most.

DimensionReasoningScore

Conciseness

Mostly efficient operational content (paths, env vars, tool parameters, config schema) rather than concept explanations, but the ~250-line body has padded passages — long justificatory asides ('SVG keeps the page self-contained, scales crisply, wraps with the layout…', the hub-registration rationale, the 'what a colleague would tell you over coffee' framing) and very long multi-clause sentences that could be tightened without losing instruction. Not 4: the trimming opportunities are recurring, not minor; not 2: the padding is justification prose, not explanations of things Claude already knows.

3 / 5

Actionability

The written guidance is unusually concrete (exact paths like ${CLAUDE_PLUGIN_DATA}/artifacts/<slug>/config.md, exact tool call parameters, an exact state-block JSON shape), but key executable details are delegated to files that do not exist in the skill directory: step 3 says 'Generate the HTML from template.html in this skill directory' and the refresh section defers the state-block field list to 'swe.md — don't improvise a different shape', yet neither file is present in the bundle. Not 4: missing core dependencies is more than a minor gap; not 2: the in-file guidance still specifies most of the work concretely.

3 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced with explicit validation checkpoints and feedback loops: step 4 re-reads the output for clipping/overflow before publishing and re-inspects after; step 8 handles publish conflicts ('WebFetch the URL… reconcile, then publish again'); the refresh section defines delta handling, missing-render recovery, and stale-data marking ('keep the previous values, mark exactly which rows or sections are stale, and never fill gaps from memory'). Not 4: validation is not merely present but looped with error-recovery paths.

5 / 5

Progressive Disclosure

Good structure in principle — a domain-neutral overview with clearly signaled, one-level-deep references ('The SWE specifics… are in swe.md', 'Generate the HTML from template.html', a Files section listing both) — but scored against the actual bundle, both referenced paths are absent from the skill directory, so the disclosed content is unreachable and the SWE workflow and template the steps depend on cannot be loaded. Not 4: broken references are a real navigation failure, not an organization gap; not 2: the SKILL.md body itself is well sectioned and the reference structure is correct.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions, an explicit 'Use when…' trigger, third-person voice, and clear negative boundaries. Its main weakness is density — the tab enumeration and swe.md parenthetical pad the length without adding triggering value, and a few natural user phrasings ('status report', 'project update') are absent.

DimensionReasoningScore

Specificity

Lists several specific concrete actions — 'Generate and publish a project status artifact — an opinionated, tabbed status page', 'refreshing it re-gathers live state, redeploys the same URL, and reports only the delta', 'pulling PR state with gh/git' — with only minor gaps (e.g., the HTML generation itself is implied, not named). Not 5: the action list is padded with structural detail ('background, plan, risks & open questions, and decisions/FAQ when they earn a tab') that inflates length without adding actions; not 3: the actions are concrete and go well beyond naming the domain.

4 / 5

Completeness

Clearly answers both: what — 'Generate and publish a project status artifact — an opinionated, tabbed status page… published with the built-in Artifact tool' — and when, with the explicit trigger phrase 'Use when a piece of work spans several workstreams and you want a shareable overview kept current', plus boundary conditions ('Needs the built-in Artifact tool'; 'Not for single-PR changes or public docs').

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'project status', 'tabbed status page', 'workstreams', 'shareable overview kept current', 'refresh', 'PR state'. Not 5: common user phrasings a teammate would actually say ('project update', 'status report', 'project dashboard', 'project overview page') are missing or only implied. Not 3: the terms present are the natural ones, not jargon-only.

4 / 5

Distinctiveness Conflict Risk

Clear niche (project-level tabbed status artifacts backed by a per-project config and refreshed as deltas) with distinct triggers, an explicit scope boundary against the general-purpose built-in Artifact tool, and a negative scope statement ('Not for single-PR changes or public docs') that keeps it from firing for the wrong skill. Minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

anthropics/claude-plugins-official

Path

plugins/project-artifact/skills/project-artifact/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.