CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-workloads

Compatibility alias for the canonical `workflow-rig` front door. Use when older prompts mention `agent-workloads` or when you need the legacy workload-planning guidance; for new work, load `workflow-rig` first.

57

Quality

66%

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 ./skills/agent-workloads/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 content is a well-organized, actionable planning skill with concrete CLI commands and a real one-level reference, but it is somewhat verbose with repeated guidance and lacks explicit validation feedback loops for its destructive/batch operations.

Suggestions

Consolidate the operator loop and the 10-step 'Until the rest exists' list into a single sequenced workflow to remove repetition and trim length.

Add an explicit validate -> fix -> retry checkpoint (e.g., gate dispatch/run on `--dry-run` or a verification step with failure handling) for destructive and batch repo operations.

Move the large command-surface flag reference and the Rules list into a separate reference file, keeping SKILL.md as a leaner overview with one-level-deep links.

DimensionReasoningScore

Conciseness

The body is domain-specific rather than padded with concepts Claude already knows, but at ~245 lines it repeats guidance (the operator loop versus the 10-step "Until the rest exists" list) and includes editorializing ("queue/restate submission theatre", "the whole bloody thing"), matching the mostly-efficient-but-tightenable score-3 anchor.

3 / 5

Actionability

It provides concrete, executable `joelclaw workload plan/dispatch/run` invocations with full flag sets plus concrete field lists and serial/parallel/chained examples, with only minor gaps such as no sample plan output, fitting score-4 over the pseudocode/incomplete score-3.

4 / 5

Workflow Clarity

The classify -> shape -> operator-loop sequence is clearly laid out, but validation checkpoints are implicit rather than gated, and this destructive/batch repo-dispatch skill lacks an explicit validate -> fix -> retry feedback loop, so the destructive-operations cap holds it at score-3.

3 / 5

Progressive Disclosure

The body is well-sectioned with clear headers and one clearly-signaled one-level-deep reference to `references/common-workloads.md` (a verified real file), with only minor organization gaps from inlining the command surface and rules bulk, matching score-4 rather than the cleanly-split score-5.

4 / 5

Total

14

/

20

Passed

Description

71%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 well-structured with an explicit Use-when trigger and clear what/when coverage, scoring highly on completeness. Its main weakness is jargon-heavy, niche-specific trigger terms and an inherent alias overlap with `workflow-rig`.

DimensionReasoningScore

Specificity

Names the domain ("Compatibility alias for the canonical `workflow-rig` front door" / "legacy workload-planning guidance") and 1-2 concrete actions (aliasing, loading `workflow-rig`), but does not comprehensively enumerate the underlying planning capabilities, matching the score-3 anchor rather than the broader score-4.

3 / 5

Completeness

It explicitly states what the skill is (a compatibility alias providing legacy workload-planning guidance) and gives a concrete "Use when older prompts mention `agent-workloads` or when you need the legacy workload-planning guidance" trigger, satisfying both what and when at the score-5 anchor.

5 / 5

Trigger Term Quality

Terms like `agent-workloads`, `workflow-rig`, and "workload-planning" are relevant to the niche but read as internal/jargon-heavy rather than natural user phrases, and common synonyms or variations are missing, fitting the score-3 anchor over the fuller coverage of score-4.

3 / 5

Distinctiveness Conflict Risk

It carves a narrow niche (legacy prompts naming `agent-workloads`) and actively redirects new work to `workflow-rig`, but as a literal alias it carries minor overlap risk with that closely related skill, placing it at score-4 rather than the minimal-conflict score-5.

4 / 5

Total

15

/

20

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
joelhooks/joelclaw
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.