CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.

Quality

72%

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 ./skills/agentic-engineering/SKILL.md

The canonical home for this skill is agentic-engineering in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an efficient, well-organized methodology playbook with zero token waste and a clear eval-gated workflow. Its main gap is actionability: it tells Claude what principles to follow but rarely shows how, with no examples or templates for evals, failure signatures, or cost tracking.

Suggestions

Add a short worked example of the eval-first loop: a sample capability eval definition, a captured failure signature, and the before/after delta comparison.

Add an error-recovery branch to the Eval-First Loop (e.g., 'If regressions appear, revert or fix before proceeding') to close the workflow validation gap.

Provide a concrete cost-tracking template (e.g., a table or list format with model, tokens, retries, wall-clock, outcome) so the Cost Discipline section is directly executable.

DimensionReasoningScore

Conciseness

The body is lean bullet-based guidance with no padding and no explanation of concepts Claude already knows; every line (e.g., "Compact after milestone completion, not during active debugging") earns its place and assumes Claude's competence.

5 / 5

Actionability

Concrete rules exist (the 15-minute unit rule, the Haiku/Sonnet/Opus tier mapping, the cost-tracking checklist), but there are no examples, templates, or commands showing how to actually define a capability eval, capture a failure signature, or structure a regression check, leaving key execution details missing.

3 / 5

Workflow Clarity

The Eval-First Loop is a clearly sequenced four-step process with an explicit compare-deltas checkpoint, but there is no error-recovery branch (what to do when the delta regresses), matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

This is a single-file skill with no bundle files; its ~57-line body is organized into well-labeled sections (principles, loop, decomposition, routing, session, review, cost) that need no external references, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

53%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 clearly names a distinctive methodology niche but reads more like a mission statement than a trigger-optimized skill description. It lacks any 'when to use' guidance and uses imperative voice instead of third person, leaving a user unsure when this skill should activate.

Suggestions

Add an explicit trigger clause, e.g., "Use when AI agents perform most implementation work on a coding task, or when planning agent delegation, eval gating, or model-tier routing."

Convert to third-person voice and enumerate concrete actions, e.g., "Gates agent implementation work behind evals, decomposes tasks into verifiable units, and routes work across Haiku/Sonnet/Opus tiers by complexity."

Include natural user phrasings such as "agents writing code", "agent workflow", or "which model should handle this" to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and three specific capabilities ("eval-first execution, decomposition, and cost-aware model routing"), which approaches the several-actions level, but the imperative "Operate as an agentic engineer" is an implied second-person voice rather than third person, triggering the 1-point voice penalty from a base of 4.

3 / 5

Completeness

The 'what' is clearly stated (eval-first execution, decomposition, cost-aware model routing), but there is no 'Use when...' clause or any equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Some relevant keywords exist ("model routing", "decomposition", "eval-first"), but the natural phrases a user would say when needing this skill (e.g., "AI agents writing code", "agent workflow", "delegating to agents") are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Distinctive terms like "eval-first execution" and "cost-aware model routing" establish a clear methodology niche with minimal conflict risk, though "agentic engineer" and "decomposition" have some overlap with general coding-workflow and planning skills, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/agentic-engineering/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.