CtrlK
BlogDocsLog inGet started
Tessl Logo

write-gods-tasks

Author task files in the GODS framework (Goal, Overview, Definition of Done, Solution). Use when the user asks to write, structure, or break down a task or plan in GODS format.

68

Quality

81%

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

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 clear, well-structured instruction-only skill that teaches the GODS format through guiding questions and four concrete worked examples. It is efficient and actionable but carries minor padding in the intro and lacks an explicit fill-in template or sequencing instruction.

Suggestions

Trim the four promotional intro bullets ('Helps to clearly articulate...', 'Makes the task transparent...', etc.) to one line, since the structure and examples already demonstrate the value.

Add an explicit blank template (e.g., a '## Template' block with 'G — Goal: ...', 'O — Overview: ...', 'D — Definition of Done: ...', 'S — Solution: ...') users can copy and fill in directly.

Add a one-line sequencing note instructing Claude to elicit or infer each of the four sections in order, including how to proceed when a section's information is missing.

DimensionReasoningScore

Conciseness

The core structure (G/O/D/S with guiding questions) and examples are lean and assume competence, but the introductory bullets ('Helps to clearly articulate...', 'Makes the task transparent...', 'Does not replace flexible processes...') are mildly promotional padding that could be trimmed; fits 'efficient; minor instances of over-explanation' rather than the fully lean 5.

4 / 5

Actionability

Provides guiding questions per section and four concrete worked examples that serve as copyable templates, giving mostly executable guidance for an instruction-only skill; not a 5 because it lacks an explicit fill-in template or schema for the user to populate directly.

4 / 5

Workflow Clarity

The G→O→D→S ordering is a clear, simple single-purpose sequence reinforced by consistent examples, but the body never explicitly instructs 'produce these four sections in order' or how to handle a task that lacks information for a section; minor sequencing gaps keep it below 5.

4 / 5

Progressive Disclosure

Well-organized with clear section headers ('What is GODS?', 'EXAMPLES OF APPLYING GODS', numbered sub-examples) and no external references needed, but at ~78 lines it slightly exceeds the under-50-lines simple-skill threshold and inlines four full examples that could be split out; good structure with minor organization gaps rather than the ideal 5.

4 / 5

Total

16

/

20

Passed

Description

87%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, third-person description that clearly states both the capability and the trigger conditions for a distinctive niche. The only gaps are minor missing synonyms in the trigger terms and not enumerating the four sections as separate actions.

DimensionReasoningScore

Specificity

Names the domain (GODS framework) and several concrete actions — 'Author task files', 'write, structure, or break down a task or plan' — matching the 'lists several specific actions; minor gaps' anchor; not a 5 because it stops short of enumerating the four GODS sections as distinct capabilities.

4 / 5

Completeness

Explicitly answers both what ('Author task files in the GODS framework...') and when ('Use when the user asks to write, structure, or break down a task or plan in GODS format') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('write, structure, or break down a task or plan', 'GODS format') but misses common synonyms like 'GODS template' or 'define a task'; fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

'GODS format' is a clear, distinctive niche with explicit triggers that are unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

18

/

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
korchasa/flowai-plugins
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.