CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-workflow-writing

Rules for writing concise, token-efficient workflow and skill files. Prevents over-building that requires costly optimization passes. Use when creating or editing workflow files, SKILL.md files, or new skill definitions.

64

Quality

80%

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/common/common-workflow-writing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, mostly actionable rules document that largely practices the conciseness it preaches. Its weaknesses are localized: an irrelevant 'Canonical response anchors' section, an empty priority header, and several grammatically broken lines that blur otherwise concrete instructions.

Suggestions

Delete the 'Canonical response anchors' section and the empty 'Priority: P0 (CRITICAL)' header — they add noise without serving the skill's purpose.

Fix the garbled lines: 'If two steps always happen together, they one step' should read 'merge them into one step'; 'No "How to X" sections: step instruction' needs a verb; and the self-check items are missing 'Is/Are'.

Restore the missing verbs in the Quick Self-Check checklist so each item is an unambiguous yes/no question the agent can answer before saving.

DimensionReasoningScore

Conciseness

The body is genuinely lean — bullet rules, a compact limits table, no prose padding — but contains minor trimmable waste: the empty "Priority: P0 (CRITICAL)" header and the irrelevant "Canonical response anchors" section ("80 lines", "delete") that serves no skill purpose.

4 / 5

Actionability

Guidance is mostly executable with concrete numbers ("80 lines", "8 rows"), explicit delete-or-keep decisions, and quoted anti-pattern examples, but garbled fragments like "If two steps always happen together, they one step" and "No 'How to X' sections: step instruction" leave minor gaps in what to actually do.

4 / 5

Workflow Clarity

As a single-purpose rules skill it provides a clear organized structure and a self-check checklist serving as its validation checkpoint, but garbled checklist items ("every table row real structure", "there any paragraphs bullet list could replace") and the dangling P0 header prevent a top score.

4 / 5

Progressive Disclosure

At ~50 lines with no external references needed and well-labeled sections, the body is well organized for a self-contained skill; however, the out-of-place "Canonical response anchors" section and the empty priority header are minor organization gaps that keep it below the clean top anchor.

4 / 5

Total

16

/

20

Passed

Description

78%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 that clearly and explicitly states both what the skill does and when to use it, with distinct triggers for the skill-authoring niche. It is somewhat light on enumerated concrete capabilities, and natural trigger variations around optimizing or refactoring existing files are missing.

Suggestions

Enumerate 2-3 concrete actions the rules enforce (e.g., 'enforces line-count limits, converts prose to bullets, moves detail to references/') to raise specificity beyond a single generic action.

Add natural trigger variations users would actually say, such as 'optimize', 'shorten', or 'refactor a workflow or skill'.

DimensionReasoningScore

Specificity

The description names the domain ("workflow and skill files") and 1-2 actions ("Rules for writing", "Prevents over-building"), but does not list several concrete actions like trimming or enforcing size limits, matching the 'domain and 1-2 concrete actions' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

It explicitly answers both what ("Rules for writing concise, token-efficient workflow and skill files") and when ("Use when creating or editing workflow files, SKILL.md files, or new skill definitions") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Use when creating or editing workflow files, SKILL.md files, or new skill definitions" covers natural create/edit triggers well, but misses common variations a user would say such as "optimize", "shorten", or "refactor" a skill/workflow.

4 / 5

Distinctiveness Conflict Risk

The workflow/skill-authoring niche with file-type-specific triggers ("SKILL.md files", "workflow files") is mostly distinct, with only minor overlap risk against generic writing-conciseness or documentation-style skills.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.github/skills/common/common-workflow-writing/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.