CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

engineer-skill

Guide for creating agent-invocable Agent Skills (SKILL.md packages auto-discovered by description). Use when users want to create or author a skill, or ask about skill structure or format. Not for user-invoked slash commands. Works across IDEs.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A highly actionable, well-sequenced authoring guide with strong validation gates and real, well-signaled bundle files. The main weaknesses are token efficiency — an off-topic question-format section pushes the body against its own budget — and under-use of references/ for the large inline tables and the priming essay.

Suggestions

Trim the "Question Format (FR-UNIVERSAL.QA-FORMAT)" section to only what applies when the skill asks the user about IDE, scope, and behavior during Phase 1, or move it to a reference file — most of its rules govern general question-asking rather than skill creation.

Move the Control Primitives Map table and/or the Priming section into references/ so the SKILL.md body sits comfortably below its own stated 20000-char cap.

Condense the dense "Two validators, two roles" paragraph into a short two-row table (validator vs. limits enforced) to cut tokens and improve scannability.

DimensionReasoningScore

Conciseness

Mostly efficient (tables, checklists, terse examples), but the "Question Format (FR-UNIVERSAL.QA-FORMAT)" section spends ~450 words on question-asking etiquette largely orthogonal to skill creation, and the "Two validators, two roles" paragraph is dense enough to need a table. Matches anchor 3 — some unnecessary explanation that could be tightened — rather than 2 since the padding is confined to a couple of sections.

3 / 5

Actionability

Copy-paste-ready commands ("deno run -A scripts/validate_skill.ts <path/to/skill-directory>", "wc -c <SKILL.md>"), a concrete directory tree, per-IDE path tables, good/bad description examples, and a self-review rubric. Matches the 5 anchor: fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Six clearly sequenced phases (Discovery through Iterate) with a BLOCKING verification gate ("do NOT finish until it exits 0"), an explicit error-recovery feedback loop ("If it fails, FIX the description and re-run"), and checklists. Matches the 5 anchor exactly.

5 / 5

Progressive Disclosure

References (references/workflows.md, references/output-patterns.md) are real, one level deep, and clearly signaled with when-to-read labels, and scripts are wired into the phase workflows. Falls short of 5 because the body sits at ~19.5k chars against its own stated 20k-char limit, with the Control Primitives Map table and the Priming section as obvious candidates for relocation to references/.

4 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description with explicit WHAT and WHEN, natural trigger terms with synonyms, and clear boundary guidance that reduces conflict risk. The only gap is that the capability list stays at the level of one macro-action rather than enumerating the concrete sub-capabilities the skill provides.

DimensionReasoningScore

Specificity

Names several concrete actions ("creating agent-invocable Agent Skills", "create or author a skill", "ask about skill structure or format") tied to a concrete artifact ("SKILL.md packages auto-discovered by description"). Falls short of the 5 anchor because it doesn't enumerate sub-capabilities like design, validation, or packaging.

4 / 5

Completeness

Explicitly answers WHAT ("Guide for creating agent-invocable Agent Skills") and WHEN ("Use when users want to create or author a skill, or ask about skill structure or format") with a concrete trigger phrase, plus an explicit exclusion. Matches the 5 anchor exactly.

5 / 5

Trigger Term Quality

Good natural-phrasing coverage with synonyms ("create or author a skill", "skill structure", "skill format") and the file name "SKILL.md". Not 5 because common variants users might say (e.g. "build a skill", "make a skill") are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (skill authoring) with distinct trigger terms, and "Not for user-invoked slash commands" explicitly de-conflicts from command-authoring skills. Minimal overlap risk — matches the 5 anchor.

5 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

korchasa/flowai-plugins

Path

plugins/flowai-devtools/skills/engineer-skill/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.