CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-first-engineering

Engineering operating model for teams where AI agents generate a large share of implementation output.

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/ai-first-engineering/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is concise and well-structured as an AI-first engineering framework, with strong token efficiency and clean sectioning. Its weakness is actionability and workflow clarity: it states principles rather than executable steps with validation checkpoints.

Suggestions

Convert the review and testing sections into concrete, ordered procedures (e.g., a numbered review checklist with explicit pass/fail validation steps) to raise workflow clarity.

Add specific executable guidance such as example eval structures or concrete review commands/templates so the directives become copy-paste ready.

Consider a short 'Use when...' or 'How to apply' callout linking each section to a triggering scenario for stronger actionability.

DimensionReasoningScore

Conciseness

The body is lean bullet-point guidance with no padding and no explanation of concepts Claude already knows, matching anchor 3 (lean and efficient; every token earns its place).

3 / 3

Actionability

Sections give concrete review/testing checklists ('behavior regressions, security assumptions, data integrity') and architectural preferences, but the guidance is high-level principles rather than executable, copy-paste-ready instructions, matching anchor 2.

2 / 3

Workflow Clarity

Content is organized into clear categories (process, architecture, review, hiring, testing) but presents no sequenced multi-step workflow and no validation checkpoints, matching anchor 2 (steps/concerns listed but checkpoints missing).

2 / 3

Progressive Disclosure

The skill is under 50 lines with no external references needed and is organized into well-labeled sections, so per the scoring note progressive disclosure scores 3 on well-organized sections alone.

3 / 3

Total

10

/

12

Passed

Description

50%

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 scopes a niche (AI-first engineering teams) but reads as a categorization rather than a capability list and omits an explicit 'Use when' trigger. It is above the vague baseline but below the strongest reference examples.

Suggestions

Add concrete actions the skill performs, e.g. 'Design process, reviews, and architecture for teams shipping AI-generated code.'

Append an explicit trigger clause, e.g. 'Use when planning reviews, process, or architecture for AI-assisted teams.'

Include natural trigger terms users would say ('AI-first engineering', 'AI code review', 'agent-friendly architecture') to improve discoverability and distinctiveness.

DimensionReasoningScore

Specificity

The phrase 'Engineering operating model for teams where AI agents generate a large share of implementation output' names a clear domain and target context, but lists no concrete actions, matching anchor 2 rather than the multi-action anchor 3 or the vague anchor 1.

2 / 3

Completeness

It states what the skill is (an operating model) and implies the audience via 'for teams where...', but lacks an explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

'engineering operating model' and 'AI agents generate...implementation output' are relevant terms, but common natural triggers like 'AI-first engineering', 'code review', or 'process design' are missing, placing it at anchor 2 (some relevant keywords, missing variations).

2 / 3

Distinctiveness Conflict Risk

The AI-first engineering niche is reasonably distinct, but the description could overlap with general engineering, code-review, or process skills and lacks distinctive triggers, matching anchor 2.

2 / 3

Total

8

/

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.