CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-dev-backend-api

Agent skill for dev-backend-api - invoke with $agent-dev-backend-api

38

1.08x
Quality

10%

Does it follow best practices?

Impact

85%

1.08x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-dev-backend-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

12%

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 verbose monologue of fictional-API pseudocode masquerading as a self-learning protocol: it is not executable, lacks validation checkpoints, and is not split across any reference files, so it adds bulk without actionable guidance.

Suggestions

Replace the pseudocode referencing reasoningBank/agentDB with either real, executable commands or remove it; every code block should be copy-paste runnable.

Cut the redundant explanation of self-learning/GNN/flash-attention concepts and collapse the repeated store/search blocks into a single concise reference.

Add explicit validation/feedback checkpoints (e.g. run tests, validate schema, fix-and-retry) to the Before/During/After sequence, and move detailed API patterns into a separate reference file linked from the body.

DimensionReasoningScore

Conciseness

The body is padded with ~170 lines of verbose TypeScript-style pseudocode that re-explains self-learning/GNN/flash-attention concepts and repeats the same store/search pattern multiple times, adding little Claude doesn't already infer.

1 / 3

Actionability

The code references non-existent APIs (reasoningBank.searchPatterns, agentDB.gnnEnhancedSearch, agentDB.flashAttention) and is non-executable pseudocode rather than concrete copy-paste-ready guidance; the responsibilities and best-practices are generic descriptions, not instructions.

1 / 3

Workflow Clarity

A loose Before/During/After sequence exists, but for risky API work (migrations, breaking changes) there are no validation checkpoints or fix-and-retry feedback loops, which caps workflow clarity below 3.

2 / 3

Progressive Disclosure

There are no bundle files in references/scripts/assets and the body is a monolithic wall of text with no links to or split-out reference files, so navigation and disclosure are poor.

1 / 3

Total

5

/

12

Passed

Description

7%

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 essentially a label with an invocation token rather than a capability statement: it names no concrete actions and gives no usage triggers, so it fails to tell Claude when or why to use it.

Suggestions

Replace the generic label with concrete capabilities, e.g. 'Design and implement RESTful and GraphQL APIs, secure authentication, and database models'.

Add an explicit 'Use when...' clause listing natural trigger terms users would say, such as 'endpoint', 'REST', 'GraphQL', 'backend route', or 'API controller'.

Drop the '$agent-dev-backend-api' invocation token from the description and instead surface the distinct backend-API niche to reduce overlap with general coding skills.

DimensionReasoningScore

Specificity

The description 'Agent skill for dev-backend-api - invoke with $agent-dev-backend-api' names no concrete actions (e.g. design, implement, test APIs); it only labels the skill, matching the vague 'Helps with documents' anchor.

1 / 3

Completeness

It weakly states 'what' (an agent skill for backend APIs) but provides no 'when to use it' / 'Use when...' trigger guidance, so it fails both halves of the completeness bar.

1 / 3

Trigger Term Quality

No natural keywords a user would say appear; the only trigger is the slash invocation token '$agent-dev-backend-api', which is technical jargon rather than user language like 'API', 'endpoint', or 'REST'.

1 / 3

Distinctiveness Conflict Risk

The 'dev-backend-api' domain is somewhat specific, but with no distinguishing trigger terms it could still overlap with other backend or general coding skills; not the level-3 clear niche.

2 / 3

Total

5

/

12

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
ruvnet/claude-flow
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.