CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

advocate

Fixture skill whose helper is addressed through both supported reference forms when assessing reference rebasing.

Quality

67%

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 ./internal/adaptertest/testdata/skill-reference-boundary/package/skills/advocate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a lean, precisely sequenced set of executable steps with no wasted tokens; it is fully self-contained and well-sectioned. Its only real gaps are missing expected-output/verification details around the helper commands.

Suggestions

State the working directory or base path the relative commands (e.g., `skills/advocate/scripts/check.sh --info`) must be run from.

Show the expected output of the helper commands so a reader can verify each step succeeded.

DimensionReasoningScore

Conciseness

The body contains zero concept explanations or padded prose; every line is a literal, purposeful test case (e.g., "Run `skills/advocate/scripts/check.sh --info`"). The repetition in Step 4 is the skill's payload, not fluff, so each token earns its place.

5 / 5

Actionability

Steps 1 and 2 give copy-paste-ready commands and Steps 3-10 are precise directives, but expected output is never shown and the working directory the relative paths resolve from is unstated, leaving minor gaps.

4 / 5

Workflow Clarity

"Process steps in order. Do not skip ahead." plus ten numbered, single-purpose steps is a clear sequence. Validation checkpoints are absent, but all operations are non-destructive reads/runs, so the destructive/batch cap at 3 does not apply.

4 / 5

Progressive Disclosure

A single self-contained file with one headed section per step; the inline examples are the skill's data and appropriately live in SKILL.md. It exceeds the under-50-line simple-skill case, keeping it just below a 5.

4 / 5

Total

17

/

20

Passed

Description

38%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 states a concrete, niche purpose but reads as internal fixture metadata rather than a user-facing skill description. It lacks any natural trigger terms and any "when to use" guidance, which caps both completeness and trigger quality.

Suggestions

Rewrite the description in third person describing user-facing actions (e.g., what the helper checks and what it outputs) instead of fixture metadata.

Add an explicit trigger clause such as "Use when ..." naming the natural phrases a user would say.

Replace jargon like "supported reference forms" and "reference rebasing" with terms users would recognize, or pair them with plain-language synonyms.

DimensionReasoningScore

Specificity

The description names its domain ("reference rebasing") and one concrete behavior ("helper is addressed through both supported reference forms"), matching the domain-plus-1-2-actions anchor; it is not entirely vague, but coverage of actions is minimal and meta.

3 / 5

Completeness

A "what" is present (a fixture exercising a helper through two reference forms), but there is no "Use when..." or equivalent trigger clause, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Terms like "reference rebasing", "supported reference forms", and "helper" are technical/meta jargon; no natural keyword a user would actually say when needing this skill appears.

1 / 5

Distinctiveness Conflict Risk

"Fixture skill" and "reference rebasing" define a clear niche with minimal overlap risk against other skills, though the absence of any distinct trigger phrases keeps it below a 5.

4 / 5

Total

11

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing, 4 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

jbaruch/agentic-context-registry

Path

internal/adaptertest/testdata/skill-reference-boundary/package/skills/advocate/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.