CtrlK
BlogDocsLog inGet started
Tessl Logo

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when AI agents perform most implementation work and humans enforce quality and risk controls.

61

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with a clear, validated eval-first workflow and concrete templates, but it mixes actionable examples with abstract principles and carries minor redundancy between the intro, Operating Principles, and When-to-Use sections.

Suggestions

Cut the redundant "When to Use This Skill" section (or fold it into the intro), since it duplicates the description and Operating Principles.

Convert abstract Operating Principles into concrete starting actions, e.g. "Define completion criteria" → "Write a one-line done condition per unit before implementation begins".

DimensionReasoningScore

Conciseness

Mostly lean with short lists and code blocks, but the opening line and the "When to Use This Skill" section largely restate the description and Operating Principles, so it could be tightened; not the padded verbosity of anchor 1.

2 / 3

Actionability

Provides concrete copy-paste templates (decomposition tree, Haiku/Sonnet/Opus routing with examples, cost-tracking block, review checklist) but interleaves them with abstract direction like "Define completion criteria before execution", so it sits between anchors 2 and 3 rather than fully executable throughout.

2 / 3

Workflow Clarity

The Eval-First Loop is a clear 4-step sequence with explicit validation (re-run evals and compare deltas) and a regression-check feedback loop, and a review checklist is provided, matching anchor 3.

3 / 3

Progressive Disclosure

Self-contained SKILL.md with no bundle files, organized into clearly labeled sections and no nested references; well-organized enough to score 3 per the simple-skill guidance.

3 / 3

Total

10

/

12

Passed

Description

75%

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 complete and reasonably specific with an explicit Use-when trigger and a distinct niche, but its capability phrasing is more conceptual/process-oriented than concrete and its trigger terms lean technical rather than naturally varied.

Suggestions

Replace conceptual process labels ("eval-first execution", "decomposition", "cost-aware model routing") with concrete verbs a user would recognize, e.g. "decompose tasks into 15-minute units, route work to Haiku/Sonnet/Opus by complexity, and run eval baselines before and after implementation".

Add natural-sounding trigger variations users might actually say (e.g. "Use when planning AI agent work, choosing which model to use for a task, or reviewing AI-generated code").

DimensionReasoningScore

Specificity

Names a domain and several actions ("eval-first execution, decomposition, and cost-aware model routing"), but these are conceptual processes rather than the concrete, multiple discrete actions of the anchor-3 example; above anchor 1 because it is not vague.

2 / 3

Completeness

Explicitly answers both what ("Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing") and when ("Use when AI agents perform most implementation work and humans enforce quality and risk controls"), matching the anchor-3 example.

3 / 3

Trigger Term Quality

Includes a "Use when AI agents perform most implementation work and humans enforce quality and risk controls" trigger, but the terms are conceptual/jargon-leaning and lack common natural variations users would say, matching anchor 2.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (agentic engineering meta-workflow with eval-first and model routing) with specific triggers unlikely to fire for unrelated skills; not the generic overlap of anchor 2.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.