CtrlK
BlogDocsLog inGet started
Tessl Logo

agentic-workflow-designer

Conversational skill that interviews users to design new agentic workflows

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/agentic-workflow-designer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 well-structured, highly actionable interview framework: concrete questions, comprehensive decision-heuristic mapping tables, a copy-paste generation template, and an explicit validation checklist with feedback loops. It is dense rather than padded, with clearly signaled external references, though some inline reference tables could arguably be split out.

DimensionReasoningScore

Conciseness

The body is information-dense with compact mapping tables and avoids explaining concepts Claude already knows; every section earns its place, though the total length is significant, fitting the efficient-but-not-maximally-lean score-4 anchor.

4 / 5

Actionability

Concrete interview questions, user-says-to-config mapping tables, a copy-paste generation template skeleton, and an exact confirmation format provide fully executable guidance covering common cases.

5 / 5

Workflow Clarity

Eight phases are explicitly sequenced with a gating rule ("Move to the next phase only after the current phase is clear"), capped by a confirmation checkpoint and a 15-item Validation Checklist with a fix-and-retry loop.

5 / 5

Progressive Disclosure

A dedicated "References (load only when needed)" section signals one-level-deep references with dual in-repo and HTTPS paths; the large inline mapping tables are runtime decision logic so inline placement is defensible, leaving minor organization gaps versus the score-5 anchor.

4 / 5

Total

18

/

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 is third-person and names a clear domain plus a couple of concrete actions, but it lacks any explicit "Use when..." trigger guidance and leans on technical phrasing rather than natural user keywords. It is competent but leaves the trigger conditions implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when a user wants to create or design an agentic workflow but hasn't specified the full requirements."

Include natural user-facing keywords/synonyms ("workflow", "automate", "GitHub Actions workflow") alongside "agentic workflows".

Tighten the action list to be more comprehensive (e.g. "interviews the user, maps requirements to workflow syntax, and generates a complete workflow file").

DimensionReasoningScore

Specificity

Names the domain ("agentic workflows") and one to two concrete actions ("interviews users", "design"), but coverage is not comprehensive, matching the score-3 anchor rather than the fuller action list of score 4.

3 / 5

Completeness

The what is clear ("interviews users to design new agentic workflows") but there is no "Use when..." clause or equivalent trigger guidance, so per the rubric cap completeness cannot exceed 3.

3 / 5

Trigger Term Quality

Terms like "agentic workflows" and "design" are relevant but skew technical and miss the natural phrases a user would say (e.g. "create a workflow", "automate"), placing it at the score-3 anchor with missing synonyms.

3 / 5

Distinctiveness Conflict Risk

"Design new agentic workflows" is a fairly distinct niche with minimal conflict risk, though it has minor overlap with sibling workflow-creation skills, fitting the score-4 anchor better than the broader score-3.

4 / 5

Total

13

/

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
Z3Prover/z3
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.