CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shipwright-pipeline

Autonomous app builder that converts plain-English descriptions into fully built, tested applications. Use when the user wants to build a new app, scaffold a project, generate a full-stack application, or create an app from a description. Trigger with "build me an app", "create a new app", "shipwright build", "scaffold a project", "generate an application".

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/ai-agency/shipwright/skills/shipwright-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A concise, well-organized skill body with a clear workflow and sensible error handling. The main weakness is actionability: the skill never shows how to actually invoke product-agent, leaving the core execution step to inference.

Suggestions

Add the concrete product-agent invocation syntax (e.g., the exact CLI command with arguments for the app description and selected stack) so step 3 of Instructions is executable rather than implied.

Show how to monitor or inspect pipeline progress (e.g., the command or output to check current phase status) so step 4 is actionable.

De-duplicate the Examples section: either replace the inline examples with a clearly signaled pointer to references/examples.md, or keep the inline examples and drop the redundant reference line.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned (Prerequisites, Supported Stacks, Instructions, Output, Error Handling, Examples, Resources) with no explanation of concepts Claude already knows; every section earns its place, matching the lean-and-efficient anchor.

5 / 5

Actionability

Some concrete guidance exists (install command, the enumerated 9 phases, stack options), but the critical execution detail is missing: step 3 says "Run `product-agent` with the app description and selected stack" without ever giving the actual CLI invocation syntax, and the Examples are skill invocations rather than executable commands, matching the incomplete-guidance anchor.

3 / 5

Workflow Clarity

The 5-step instruction sequence is clear and includes monitoring the 9-phase pipeline plus an Error Handling section, but validation exists only inside the delegated pipeline and phase failures are reported to the user rather than fed into an explicit fix-and-retry loop, matching the clear-sequence-with-minor-validation-gaps anchor.

4 / 5

Progressive Disclosure

Good structure with a real, one-level-deep reference (${CLAUDE_SKILL_DIR}/references/examples.md, verified to exist), but the body's inline Examples section substantially duplicates that reference and the pointer is buried in a trailing Resources list rather than clearly signaled where examples are discussed, matching the good-structure-with-minor-gaps anchor.

4 / 5

Total

16

/

20

Passed

Description

78%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: it clearly states what the skill does and when to use it, with a solid set of natural trigger phrases. The main limitation is that the capability statement is a single broad action rather than several distinct concrete actions.

DimensionReasoningScore

Specificity

The description names the domain and 1-2 concrete actions ("converts plain-English descriptions into fully built, tested applications") but does not list several distinct specific actions, matching the anchor for domain plus 1-2 actions rather than the several-actions anchor above.

3 / 5

Completeness

It explicitly answers both what ("Autonomous app builder that converts plain-English descriptions into fully built, tested applications") and when ("Use when the user wants to build a new app, scaffold a project..."), plus concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered ("build me an app", "create a new app", "scaffold a project", "generate an application", "shipwright build"), but a few common variants (e.g., "make an app", "new project") are missing, which fits the good-coverage-with-gaps anchor rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The app-generation-from-description niche with its own triggers ("shipwright build") is mostly distinct, with only minor overlap risk against general code-generation or scaffolding skills, matching the mostly-distinct anchor.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/shipwright/skills/shipwright-pipeline/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.