CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentic-workflows

Route gh-aw design, creation, diagnosis, patching, active debugging, and upgrade requests to the right strategies.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

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 body is a well-structured, actionable router: precise condition-to-path mappings, a clear overlay/precedence rule, and true progressive disclosure that inlines no detail content. Its weaknesses are token cost from the duplicated 81-file listing, the unspecified mechanism for loading remote files, and implicit rather than explicitly numbered workflow steps.

Suggestions

Deduplicate the file list against the routing table — either list only files not already routed, or group the 81 entries by category (syntax, debugging, safe-outputs, token optimization, etc.) so navigation is easier and tokens are saved.

Specify how to load the remote files (e.g., an exact gh CLI command or URL pattern for github/gh-aw), since the body notes they are 'not available locally' but gives no mechanism.

State the dispatcher flow as a short numbered sequence (identify task type → load matched prompt → load overlay if present → follow) instead of leaving the ordering implied across sections.

DimensionReasoningScore

Conciseness

The body is terse and free of concept explanations Claude already knows, but the 81-entry flat file list substantially duplicates paths already named in the routing table, which 'could be tightened'. It is not a 2 because there is no padded prose or unnecessary explanation — the verbosity is structural duplication rather than over-explanation.

3 / 5

Actionability

The routing table gives concrete, executable mappings from specific conditions (e.g., "'model: auto' failures", "install-step 404s after a version pin") to exact file paths, matching 'mostly executable guidance; concrete commands with minor gaps'. It is not a 5 because the instruction to "Load these files from github/gh-aw (they are not available locally)" never states the mechanism (command or URL pattern) for loading them.

4 / 5

Workflow Clarity

The dispatcher sequence is coherent and ordered (identify task type → load the matching prompt → load the repository overlay 'after loading the matched prompt/skill' with an explicit precedence rule → follow it), with a decision checkpoint ('ask a clarifying question if the correct prompt is unclear'). It is not a 5 because the steps are implied across sections rather than explicitly sequenced, and there is no guidance for recovering when a match is wrong or ambiguous.

4 / 5

Progressive Disclosure

The body is a pure overview pointing to one-level-deep references with clear per-task signals and no inlined detail content, matching 'good structure; most content appropriately placed'. It is not a 5 because the undifferentiated 81-file flat list is harder to navigate than categorized references and duplicates the routing section's paths.

4 / 5

Total

15

/

20

Passed

Description

58%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 appropriately concise, listing multiple concrete task actions for a clearly niched domain. Its main weaknesses are the missing explicit 'Use when...' trigger clause and reliance on the jargon abbreviation 'gh-aw' without natural synonyms, which weaken trigger-term quality and completeness.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks to design, create, debug, or upgrade GitHub Agentic Workflows (gh-aw)'.

Spell out 'GitHub Agentic Workflows' alongside the gh-aw abbreviation and include natural synonyms users would say, such as 'troubleshoot', 'fix', 'edit', and 'update workflows'.

Reflect more of the routed task types (e.g., analyzing runs, optimizing tokens, creating reports or shared components) to close the coverage gaps in the action list.

DimensionReasoningScore

Specificity

The description enumerates several concrete actions ("design, creation, diagnosis, patching, active debugging, and upgrade") tied to a named domain, matching the 'several specific actions; minor gaps' anchor. It is not a 5 because routed capabilities like run analysis, token optimization, and report generation are omitted from the action list.

4 / 5

Completeness

The 'what' is clear ("Route ... requests to the right strategies"), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by naming request types, which per the guidelines caps completeness at 3. It is not a 2 because the 'what' is concrete and specific rather than vague.

3 / 5

Trigger Term Quality

Task verbs like "design", "diagnosis", and "upgrade" are terms users would naturally say, but the only domain noun is the jargon abbreviation "gh-aw" — the full phrase "GitHub Agentic Workflows" and common synonyms such as "troubleshoot", "fix", or "edit" are missing. This fits 'some relevant keywords but missing common variations' better than the level-4 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

Scoping to "gh-aw" gives the skill a clear niche with distinct triggers, matching 'mostly distinct; minor overlap risk'. It is not a 5 because broad verbs like "diagnosis" and "design" could overlap with general GitHub Actions or debugging skills, and the gh-aw abbreviation alone may not disambiguate for users who say 'agentic workflows'.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Azure/azure-sdk-for-net

Path

.github/skills/agentic-workflows/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.