0protocol
Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.
59
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
17%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description lists technical capabilities but fails to explain them in accessible terms or provide any guidance on when to use the skill. The jargon-heavy language ('publicly attest to behavior') would not match natural user queries, and the complete absence of trigger guidance severely limits Claude's ability to select this skill appropriately.
Suggestions
Add a 'Use when...' clause with natural trigger terms like 'plugin security', 'credential management', 'agent identity', or 'verify agent behavior'
Replace or supplement technical jargon with plain language explanations (e.g., 'verify and secure agent plugins' instead of just 'sign plugins')
Clarify the domain context - specify what type of agents and what scenarios this applies to (e.g., 'For AI agent security and identity management')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names specific actions ('sign plugins', 'rotate credentials', 'attest to behavior') but uses technical jargon without explaining what these mean concretely or what the skill actually does with them. | 2 / 3 |
Completeness | Describes capabilities (what) but completely lacks any 'Use when...' clause or explicit trigger guidance. No indication of when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Uses highly technical terms ('sign plugins', 'rotate credentials', 'attest') that users are unlikely to naturally say. Missing common variations or natural language triggers like 'security', 'authentication', or 'verify'. | 1 / 3 |
Distinctiveness Conflict Risk | The combination of 'plugins', 'credentials', and 'attest' is somewhat specific to a security/identity domain, but 'credentials' could overlap with password managers or authentication skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently communicates a complex identity protocol. The content is highly actionable with executable examples and excellent organization. The main gap is the absence of validation steps in the workflow—there's no guidance on confirming operations succeeded or recovering from failures.
Suggestions
Add validation steps after each mcporter call showing how to verify the expression was recorded (e.g., query the expression log or check return values)
Include error handling guidance for common failure modes (network issues, invalid payloads, signature failures)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what signing, hashing, or Ed25519 are. Every section earns its place with concrete information Claude needs. | 3 / 3 |
Actionability | Provides complete, copy-paste ready commands with realistic payloads. The mcporter call examples include full JSON structures with meaningful field values, not pseudocode. | 3 / 3 |
Workflow Clarity | The three-step canonical use case shows a logical sequence (sign → attest → transfer), but lacks validation checkpoints. No guidance on verifying signatures succeeded or handling errors. | 2 / 3 |
Progressive Disclosure | Clean structure with quick start, tool reference table, canonical examples, and well-signaled external resources. References are one level deep and clearly organized. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.