agentic-workflow-designer

Conversational skill that interviews users to design new agentic workflows

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

73%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 content is a well-sequenced, highly actionable interview skill with explicit checkpoints and a validation checklist. Its main weakness is conciseness: the exhaustive Network Mapping table and several heuristics bloat the body and would be better moved to referenced files.

Suggestions

Move the large Network/Tool/Pattern heuristic mapping tables into separate reference files and link to them, keeping only a compact summary in SKILL.md to improve conciseness and progressive disclosure.

Tighten or prune rarely-used network-ecosystem rows (e.g. niche languages) to reduce tokens that do not earn their place for the common case.

Confirm the listed in-repo reference paths (e.g. .github/aw/network.md) actually resolve, or note that they point to an external repo, to avoid dangling references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient directive prose (phases, mapping tables, templates), but the very large Network Mapping table enumerates dozens of language/package ecosystems that pad the skill without clear payoff, which could be moved to a reference.	3 / 5
Actionability	It provides concrete, executable guidance: exact questions to ask, decision-heuristic mapping tables, a confirmation format, and a copy-paste-ready workflow skeleton template with real field names.	4 / 5
Workflow Clarity	The interview is explicitly sequenced into Phases 1–8 with 'move to next phase only after the current phase is clear', a Confirmation gate, a generation step, and a 15-item Validation Checklist serving as explicit checkpoints/feedback loops.	5 / 5
Progressive Disclosure	Structure is strong with clear sections and a 'References (load only when needed)' block listing one-level-deep in-repo and HTTPS references; however no bundle files exist in ./references, ./scripts, or ./assets, and large mapping tables are inlined rather than split into reference files, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

46%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 states a clear purpose but omits explicit 'Use when...' trigger guidance, which caps completeness, and it is thin on natural trigger phrases. Specificity is moderate with only a couple of concrete actions named.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when a user wants to design a new agentic workflow but has not written the workflow syntax yet'.

Include natural trigger phrases users would say, such as 'design a workflow', 'create an agentic workflow', or 'workflow template'.

List a couple more concrete actions (e.g. 'interviews the user, maps requirements to workflow syntax, generates a workflow .md file') to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ('agentic workflows') and two concrete actions ('interviews users', 'design new agentic workflows'), but these are minimal and generic compared to a comprehensive multi-action list.	3 / 5
Completeness	There is a clear 'what' (interviews users to design agentic workflows), but no explicit 'when' / 'Use when...' clause, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	It includes 'agentic workflows' but lacks the natural trigger phrases users would actually say (e.g. 'create a workflow', 'design a workflow', 'agentic workflow'); only one generic keyword is present.	2 / 5
Distinctiveness Conflict Risk	The niche is fairly specific ('agentic workflows' design) and unlikely to collide with unrelated skills, though 'workflow' alone is broad enough to risk minor overlap with general workflow tooling.	4 / 5
	Total	12 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: bradygaster/squad
Path: .github/skills/agentic-workflow-designer/SKILL.md
Commit: 9587fcd

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.