CtrlK
BlogDocsLog inGet started
Tessl Logo

opensource-pipeline

Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'.

72

Quality

88%

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

The canonical home for this skill is tdg-personal/opensource-pipeline

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The skill is highly actionable with an excellent validation-gated workflow, but is held back by redundancy across the repeated agent-spawn blocks and a monolithic structure that inlines three agent prompts rather than splitting them into reference files.

Suggestions

Consolidate the three repeated Agent() spawn blocks into a single parameterized template and drop the Final Review file list that duplicates Step 5's outputs, to tighten conciseness.

Extract the forker, sanitizer, and packager agent prompts into separate reference files (e.g. references/forker.md) and point to them from SKILL.md, improving progressive disclosure toward a lean overview.

Consider bundling the referenced sub-agents (opensource-forker/sanitizer/packager) or the cited security-review skill so the cross-references resolve to actual files.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no concept explanations Claude already knows, but repeats the Agent() spawn template three times and the Final Review block restates files already enumerated in Step 5, so it could be tightened. It is not a 3 because of that redundancy and length (~250 lines), and not a 1 because it avoids padded background exposition.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: exact Agent() spawn calls with prompts, exact bash ('mkdir -p $HOME/opensource-staging/', 'gh repo create ... --public --source=. --push'), and concrete path-resolution logic. It is not a 2 because there is no pseudocode or missing key details.

3 / 3

Workflow Clarity

A clearly sequenced 7-step pipeline with an explicit validation checkpoint (sanitizer PASS/FAIL gate) and a feedback loop (FAIL -> fix -> re-scan, max 3 retries) before proceeding, matching the score-3 anchor. It is not a 2 because validation and error recovery are explicit, not implicit.

3 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the body is a single ~250-line monolith with three detailed agent prompts inline that could be split out; sections are well-organized but content is not appropriately separated. It is not a 3 because it is not a lean overview with one-level-deep references, and not a 1 because organization is clear rather than a wall of text with nested references.

2 / 3

Total

10

/

12

Passed

Description

100%

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

The description is concise, third-person, and cleanly states both the staged pipeline capabilities and explicit trigger phrases. It hits all four dimensions at the top anchor with no verbosity or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('fork, sanitize, and package private projects') and names the pipeline stages plus the three chained agents, matching the score-3 anchor for multiple specific concrete actions. It is not a 2 because it goes beyond naming a domain and a few actions to enumerate the full staged pipeline.

3 / 3

Completeness

Explicitly answers both 'what' (fork, sanitize, package pipeline for safe public release) and 'when' via a dedicated 'Triggers:' clause. It is not a 2 because the 'when' is stated explicitly rather than merely implied.

3 / 3

Trigger Term Quality

Provides natural phrases a user would actually say — 'open source this', 'make this public', 'prepare for open source', plus the '/opensource' command — giving good coverage of common variations. It is not a 2 because it includes several natural phrasings rather than a single relevant keyword.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (sanitizing private repos for public release) with distinct triggers unlikely to fire for unrelated skills. It is not a 2 because the domain and triggers are specific enough to avoid overlap with general packaging or git skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.