CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-dev-backend-api

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

49

1.08x
Quality

26%

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

The canonical home for this skill is agent-dev-backend-api in ruvnet/claude-flow

SKILL.md
Quality
Evals
Security

Quality

Content

31%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 padded mix of inlined agent-config YAML and fictional/non-executable self-learning code with no real validation workflow and no external reference structure. It reads as aspirational feature marketing rather than actionable guidance Claude can follow.

Suggestions

Remove the inlined YAML agent-config block (or move it to a separate reference file) and keep only the markdown guidance in SKILL.md.

Replace the fictional reasoningBank/agentDB/GNN examples with real, executable steps Claude can take, or delete them if no such library exists.

Add explicit validation checkpoints (e.g. run tests, confirm endpoints respond) to the Before/During/After sequence, especially before destructive changes like migrations.

DimensionReasoningScore

Conciseness

The body is noticeably verbose and padded: a ~170-line inlined YAML agent-config block plus fictional self-learning/GNN/flash-attention TypeScript sections studded with buzzwords ('+12.4% accuracy', '4-7x faster', 'self-learning'). It does not explain basics Claude already knows, so it stays above 1, but multiple sections are unnecessary padding.

2 / 5

Actionability

The TypeScript examples call non-existent APIs (reasoningBank.searchPatterns, agentDB.gnnEnhancedSearch, agentDB.flashAttention) and the shell hooks contain broken syntax ('2>$dev$null'), so the code is not executable; the rest is high-level responsibility/best-practice lists rather than concrete steps, matching 'Minimal concrete guidance; high-level hints.'

2 / 5

Workflow Clarity

A rough Before/During/After sequence is present with an implicit test-run checkpoint ('runTests()', 'npm run test:api'), but validation is not an explicit checkpoint and the skill touches destructive operations (DB migrations), so per the destructive-operations cap it cannot exceed 3.

3 / 5

Progressive Disclosure

No bundle files exist and the entire 170-line agent-config YAML is inlined directly in SKILL.md — content that clearly belongs in a separate file — with section headers providing only minimal structure, matching 'Minimal structure; content that clearly belongs in separate files is inlined.'

2 / 5

Total

9

/

20

Passed

Description

21%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 a bare label plus an invocation hint: it names a domain but lists no capabilities, includes no natural trigger terms, and provides no usage guidance. It is only marginally better than the worst anchor because it at least specifies the backend-API niche.

Suggestions

Replace the description with concrete actions, e.g. 'Designs and implements REST/GraphQL endpoints, authentication, and data models. Use when the user asks to create endpoints, add routes, or build backend APIs.'

Add a 'Use when...' clause with natural trigger terms users actually say (endpoint, route, controller, REST, GraphQL).

Drop the '$agent-dev-backend-api' invocation token from the description — it is invocation metadata, not a capability statement.

DimensionReasoningScore

Specificity

The phrase 'Agent skill for dev-backend-api' names the domain (backend API development) but states no concrete actions, only that it is 'a skill' — fitting the anchor 'Names the domain but actions are minimal or generic.' It is above 1 because a specific domain is named, but not 3 since zero concrete capabilities are listed.

2 / 5

Completeness

It offers a vague 'what' ('Agent skill for dev-backend-api') and no 'when' / 'Use when...' guidance at all, matching 'Has a vague what and no when.' The missing trigger clause also caps completeness well below 4.

2 / 5

Trigger Term Quality

The only terms are 'dev-backend-api' and the invocation token '$agent-dev-backend-api', which are technical slash-command jargon rather than natural phrases a user would say; this matches 'No natural keywords; only technical jargon.'

1 / 5

Distinctiveness Conflict Risk

The named niche 'backend-api' is somewhat specific and the explicit invocation token adds distinctiveness, but the description is generic enough to overlap with other backend/server skills, fitting 'Somewhat specific but could still overlap with similar skills.'

3 / 5

Total

8

/

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
ruvnet/ruflo
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.