CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

56

Quality

65%

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

68%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 an efficient, well-structured authoring standard with concrete rules and a size-limits table. Its main weakness is the absence of an explicit validation/feedback loop in its prescribed workflow.

Suggestions

Add an explicit validate→fix→retry checkpoint to the 'Workflow Structure (Required order)' section so authored workflows are verified before saving.

Expand references/example.md from its stub into a real, loadable template or worked example so the references/ path earns its place.

Tighten or remove the 'Canonical response anchors' section if it duplicates rules already stated in Core Rules or Anti-Patterns.

DimensionReasoningScore

Conciseness

Mostly lean bullet rules with no concept re-explanation, but the 'Canonical response anchors' section and a couple of imperfectly worded self-check lines keep it just below fully lean.

4 / 5

Actionability

Concrete do/don't rules plus a specific size-limits table give mostly executable guidance, though some rules state principles ('Templates, not examples') rather than directly executable steps.

4 / 5

Workflow Clarity

Required structure order and a self-check checklist provide a rough sequence, but there is no explicit validate→fix→retry feedback loop and the structure block stays abstract.

3 / 5

Progressive Disclosure

Well-organized sections with one-level-deep references signaled in the size-limits table and a real references/example.md bundle present, though the bundle is a near-empty stub.

4 / 5

Total

15

/

20

Passed

Description

62%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 clearly states purpose and provides an explicit 'Use when' trigger, landing it solidly above average. It could be sharper with more comprehensive, concrete action verbs and more natural trigger synonyms.

Suggestions

Add concrete action verbs (e.g., 'audits', 'trims', 'restructures') alongside the abstract 'Rules for writing' framing.

Broaden trigger terms with natural phrases a user would say (e.g., 'make this skill shorter', 'trim my workflow', 'optimize skill tokens').

Tighten the 'what' to name the specific checks performed (line-count limits, table-row limits, anti-pattern removal).

DimensionReasoningScore

Specificity

Names the domain and a couple of concrete actions (writing concise files, preventing over-building) but the actions are abstract rather than a comprehensive list, fitting 'Names domain and 1-2 concrete actions'.

3 / 5

Completeness

Has a clear 'what' and an explicit 'Use when...' clause, but the 'when' enumerates file types rather than concrete natural trigger phrases, so it is not a full 5.

4 / 5

Trigger Term Quality

Includes relevant triggers like 'creating or editing workflow files, SKILL.md files' but misses common synonyms/variations a user might naturally say, fitting 'Some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (workflow/skill authoring standard) with specific file-pattern triggers and only minor overlap risk with adjacent authoring skills.

4 / 5

Total

14

/

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.

Validation14 / 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
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.