CtrlK
BlogDocsLog inGet started
Tessl Logo

0protocol

Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.

55

Quality

61%

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 ./public/skills/0isone/0protocol/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 minimal and well-organized but only covers installation; it provides no executable guidance or workflow for the skill's actual capabilities (signing, credential rotation, attestation).

Suggestions

Add concrete, executable examples or commands for at least the common cases of signing plugins and rotating credentials.

Include a brief usage workflow showing what to do after install, with any validation step if operations are destructive or batch-oriented.

If detailed API/behavior docs exist, link them as one-level-deep references rather than leaving the body install-only.

DimensionReasoningScore

Conciseness

The body is extremely lean — a restated one-line purpose plus a single install command — with no padding or over-explanation, fitting 'lean and efficient; every token earns its place'.

5 / 5

Actionability

Only the install command is concrete and executable; the core operations (signing plugins, rotating credentials, attesting behavior) have no code, commands, or specific steps, matching 'minimal concrete guidance; missing the specific steps to execute'.

2 / 5

Workflow Clarity

The install step is a single unambiguous action, but the actual usage workflow for the skill's stated purpose is entirely absent, so it does not reach the higher anchors that require a complete sequenced process.

3 / 5

Progressive Disclosure

Under 50 lines with no need for external references and clearly sectioned (# 0protocol, ## Install), qualifying for the simple-skill exception that allows a 5 with just well-organized sections.

5 / 5

Total

15

/

20

Passed

Description

58%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 names three concrete capabilities in third person but omits any explicit trigger guidance, leaving the 'when to use' question unanswered. Trigger-term coverage is narrow with no synonyms or variations.

Suggestions

Add a 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when an agent needs to sign plugins, rotate credentials without losing its identity, or publicly attest to behavior').

Broaden trigger terms with natural synonyms and any relevant file extensions or command names users would say.

Consider noting the distinct niche more explicitly to reduce overlap with generic credential-management skills.

DimensionReasoningScore

Specificity

Lists three concrete actions ('sign plugins, rotate credentials without losing identity, and publicly attest to behavior'), matching the 'several specific actions; minor gaps' anchor rather than the 5-anchor's comprehensive multi-action coverage.

4 / 5

Completeness

The description gives a clear 'what' but no 'when' / 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant niche terms (sign plugins, rotate credentials, attest to behavior) are present but there are no synonyms, file extensions, or common variations, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The agent identity/attestation niche is mostly distinct, though 'rotate credentials' and 'sign plugins' could overlap with generic credential-management skills, matching 'mostly distinct; minor overlap risk'.

4 / 5

Total

14

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Demerzels-lab/elsamultiskillagent
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.