CtrlK
BlogDocsLog inGet started
Tessl Logo

clawwork

ClawWork economic survival protocol — work/learn daily cycle

58

Quality

67%

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 ./clawmode_integration/skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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 tight, well-structured instruction skill with concrete tool invocations, explicit thresholds, and a clear daily workflow. Its only weakness is minor redundancy that keeps conciseness from a perfect score.

DimensionReasoningScore

Conciseness

Mostly efficient — tables and terse bullets assume Claude's competence and avoid explaining known concepts — but a few lines restate information (e.g., 'Every API call costs money' restates the intro) and could be tightened.

2 / 3

Actionability

Provides a concrete tools table, specific invocation examples like decide_activity(activity="work", reasoning="..."), explicit numeric thresholds, and iteration guidance ('submit by iteration 10–12 out of 15').

3 / 3

Workflow Clarity

The daily workflow is clearly sequenced (Analyse → Decide → Execute → Stop) for a simple single-purpose process; no destructive/batch operations are present that would require validation checkpoints.

3 / 3

Progressive Disclosure

A single self-contained file under 50 lines with well-organized sections and no need for external references, which the rubric permits to score 3 on progressive disclosure.

3 / 3

Total

11

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 identifies a clear niche and its core work/learn cycle but provides no explicit usage triggers, leaving the 'when' unstated. It is adequate but generic enough to cap several dimensions at 2.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should activate this skill (e.g., 'Use when running a ClawWork economic survival session or when the prompt presents a work/learn daily-cycle task').

List concrete actions more specifically rather than 'work/learn daily cycle' (e.g., 'decide whether to work or learn, submit work artifacts for evaluation, and manage token costs to stay solvent').

Include natural trigger terms a user would actually say, such as 'ClawWork session', 'economic survival', 'maintain positive balance', or 'submit work for payment'.

DimensionReasoningScore

Specificity

Names the domain ('economic survival protocol') and two concrete actions ('work/learn daily cycle'), but the actions are high-level and not comprehensive.

2 / 3

Completeness

States the 'what' (economic survival protocol, work/learn cycle) but omits any 'when' — there is no 'Use when...' clause, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

'economic survival', 'work/learn', 'daily cycle' are somewhat relevant but lean abstract/jargony rather than natural user phrasing, and miss common variations.

2 / 3

Distinctiveness Conflict Risk

'ClawWork economic survival protocol' is a recognizable niche, but the weak/absent explicit triggers mean it could still overlap with generic productivity or task-management skills.

2 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
HKUDS/ClawWork
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.