CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

publish

Publish Seed specification as GitHub Issues for team-based project management

Quality

76%

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 ./skills/publish/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 body is an exemplary lean, step-sequenced workflow: exact gh commands, explicit stop conditions, a duplicate-check gate, and a plan-review feedback loop before batch issue creation. The only notable gaps are that Epic/Task creation commands are structural rather than verbatim, and the seed-format mapping tables could be split into a reference file.

DimensionReasoningScore

Conciseness

The body is lean throughout: compact field-mapping tables, exact commands with flags, and no explanations of concepts Claude already knows. Every token earns its place, matching the anchor-5 example of assuming Claude's competence.

5 / 5

Actionability

Mostly executable guidance: fully specified commands for prerequisites, repo detection, duplicate search, and label creation, plus the heredoc body pattern. It falls short of anchor 5 because the Epic and Task `gh issue create` commands are described structurally (titles, labels, body sections) rather than given as complete copy-paste invocations.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints (gh presence, auth status, duplicate check with a cancel path) and a feedback loop in Step 6 (show plan, ask, modify, re-show) before the batch creation. This matches anchor 5's explicit validation and error-recovery loops rather than anchor 4's "minor validation gaps".

5 / 5

Progressive Disclosure

Good structure with clear step sections and no broken or buried references (no bundle files are referenced and none exist). It scores 4 rather than 5 because the two inline seed-format field-mapping tables are reference material that could live in a separate file, and at ~107 lines the skill exceeds the simple-skill exception for a content-free-structure 5.

4 / 5

Total

18

/

20

Passed

Description

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

The description is concise and names a concrete, niche capability, but it lacks any "when to use" trigger guidance and only hints at the full set of actions (Epic plus Task creation, duplicate checking). Adding an explicit trigger clause and one or two more concrete actions would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to publish a Seed to GitHub, create an Epic with Task issues, or move a Seed specification into project management."

Enumerate the key actions so coverage is comprehensive: "Converts a Seed into a GitHub Epic issue plus Task issues with acceptance-criteria checklists via the gh CLI, with duplicate detection."

Include natural trigger synonyms such as "publish seed", "create GitHub issues from seed", and "set up project tracking" to improve trigger-term quality.

DimensionReasoningScore

Specificity

"Publish Seed specification as GitHub Issues" names the domain and one concrete action, but does not list the several specific actions the skill performs (Epic/Task issue creation, duplicate detection, labeling). It fits anchor 3 (1-2 concrete actions, not comprehensive) rather than 4, which requires a list of several specific actions.

3 / 5

Completeness

The description clearly answers "what" (publishes a Seed specification as GitHub Issues) but has no "Use when..." clause or equivalent explicit trigger guidance; "when" is only weakly implied. Per the judging guidelines, a missing trigger clause caps completeness at 3, and it does not reach 4 because the "when" is not merely under-specified, it is absent.

3 / 5

Trigger Term Quality

Relevant keywords exist ("Publish", "Seed specification", "GitHub Issues", "team-based project management"), but "Seed specification" is project-specific jargon and common natural variations or synonyms are missing. This matches anchor 3 rather than 4, since keyword coverage is not comprehensive.

3 / 5

Distinctiveness Conflict Risk

"Seed specification" establishes a clear niche term making the skill mostly distinct, though "GitHub Issues" and "team-based project management" could overlap with generic issue-management skills. This fits anchor 4 (mostly distinct, minor overlap risk) rather than 5, whose example also includes explicit distinct trigger phrases.

4 / 5

Total

13

/

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

Q00/ouroboros

Path

skills/publish/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.