CtrlK
BlogDocsLog inGet started
Tessl Logo

agentic-workflows

Route gh-aw workflow design/create/debug/upgrade requests to the right prompts.

58

Quality

66%

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

Fix and improve this skill with Tessl

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

Quality

Content

67%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 skill is a well-structured dispatcher with concrete task-to-file routing and clear precedence rules, but it carries a large undifferentiated file listing that undercuts conciseness. Tightening that list to the routed files would notably improve it.

Suggestions

Replace the 68-file enumeration with just the files referenced by the routing map, or move the full catalog to a separate index file referenced once.

Add a brief validation/confirmation step (e.g., 'If no task type matches, ask the user to clarify before loading a prompt') to strengthen workflow clarity.

Reconcile the 'Read only the files you need' instruction with the exhaustive list so the guidance is not self-contradictory.

DimensionReasoningScore

Conciseness

The routing section is lean, but the 68-item file enumeration (lines 20-87) contradicts 'Read only the files you need' and pads the skill with many paths not used for routing; it could be trimmed to the routed set, so it is mostly efficient but noticeably loose.

3 / 5

Actionability

Concrete task-to-file mappings like 'Create new workflows: .github/aw/create-agentic-workflow.md' give executable load targets with minor gaps; it is instruction-only but actionable rather than abstract.

4 / 5

Workflow Clarity

The dispatcher sequence (identify task type -> load matching prompt/skill -> follow it, with optional overlay precedence) is clear and ordered; no validation checkpoints are present but none are warranted for non-destructive routing, so minor gaps keep it at 4.

4 / 5

Progressive Disclosure

The body is an overview that signals one-level-deep references via a clean task->file routing map; the undifferentiated 68-file list is an organization gap, but no bundle files exist locally and references are external and clearly signaled.

4 / 5

Total

15

/

20

Passed

Description

66%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 specific and names concrete workflow actions with a clear niche, but it omits an explicit 'Use when' trigger clause, which caps its completeness. Adding a trigger phrase would lift it into the top band.

Suggestions

Append an explicit trigger clause such as 'Use when a user asks to design, create, update, debug, or upgrade GitHub Agentic Workflows.'

Add natural synonyms ('build', 'fix', 'refactor workflows') to broaden trigger-term coverage.

Mention 'update' alongside design/create/debug/upgrade so the description's action list matches the body.

DimensionReasoningScore

Specificity

Names the domain (gh-aw workflows) and lists several concrete actions — 'design/create/debug/upgrade' — plus the routing action; not a comprehensive 5 because update/shared/report tasks from the body are absent from the description.

4 / 5

Completeness

There is a clear 'what' (route requests to the right prompts) but no explicit 'Use when...' trigger clause; per the rubric a missing explicit trigger clause caps completeness at 3 even though the action list weakly implies when.

3 / 5

Trigger Term Quality

Natural verbs users say ('design', 'create', 'debug', 'upgrade', 'workflow') are present and relevant, but 'gh-aw' is jargon and common synonyms like 'build' or 'fix' are missing, so it sits below a 5.

4 / 5

Distinctiveness Conflict Risk

The 'gh-aw workflow' niche is distinct with task-specific triggers, but the bare action verbs could overlap marginally with general coding-workflow skills, keeping it just below a 5.

4 / 5

Total

15

/

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
primer/react
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.