CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dynamic-workflow-mode

Design task-local harnesses, eval gates, and reusable skill extraction for Claude dynamic workflow mode and other adaptive agent harnesses. Use when building a task-local harness, adding eval gates, or extracting a reusable skill from ad-hoc work.

Quality

82%

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 well-structured, actionable methodology guide: the harness template, decision tree, and eval-gate table give concrete, validated workflows, and validation checkpoints are baked into the loop. The main weaknesses are the heavy inline boundary-policy section, one unactionable ECC reference, and no use of reference files to split deeper detail out of SKILL.md.

Suggestions

Move the "Preserve Input Boundaries" policy prose and synthetic-case table into a references/ file (e.g. references/input-boundaries.md), keeping a short summary plus a clearly signaled one-level-deep link in SKILL.md.

Add a concrete example command or expected pass signal for at least one row of the Eval Gates table (e.g. a sample focused-test or dry-run invocation) so the cheapest-reliable-gate guidance is executable, not just descriptive.

Replace or qualify "the ECC control pane or state-store-backed scripts" with an actionable fallback (e.g. a tracked status file path and format) since no such scripts ship in this skill's bundle.

DimensionReasoningScore

Conciseness

The body is dense and instructional with no explanations of concepts Claude already knows, but the ~30-line "Preserve Input Boundaries" section repeats binding rules in policy-style prose (e.g. "without retroactively treating earlier substitutions as authorized; preserve all tool bindings outside that scoped change") that could be trimmed — 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

A copy-paste harness template, a five-rule decision tree, a work-type-to-eval-gate table, and a synthetic-case table with expected routing give mostly executable guidance; it falls short of fully executable because eval-gate entries lack example commands and "ECC control pane or state-store-backed scripts" points to no concrete artifact.

4 / 5

Workflow Clarity

The template Loop is a numbered sequence with an explicit validation checkpoint ("Run eval checks") and failure handling ("Stop on failed gate, unclear ownership, or unsafe external action"), plus hold-and-ask recovery for ambiguous boundaries; however, the end-to-end process must be assembled across four separate sections and there is no fix-and-revalidate cycle, leaving minor validation gaps.

4 / 5

Progressive Disclosure

Ten clearly headed sections give good structure for a self-contained ~155-line skill with no bundle files, but everything is inline — the boundary policy and case table are candidates for a references/ file — and the ECC/control-pane mention references nothing in the bundle, so it is not a fully well-split overview.

4 / 5

Total

16

/

20

Passed

Description

83%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: third-person, concise, with an explicit 'Use when...' clause covering concrete triggers and a clear what. The main gaps are a missing capability (control-pane checkpoints) and a few natural trigger synonyms that appear in the body but not the description.

DimensionReasoningScore

Specificity

"Design task-local harnesses, eval gates, and reusable skill extraction" lists three concrete actions in a named domain ("Claude dynamic workflow mode"), matching 'several specific actions; minor gaps' — it omits the control-pane/observability capability the body covers, so it falls short of the comprehensive level-5 anchor.

4 / 5

Completeness

It clearly answers both what ("Design task-local harnesses, eval gates, and reusable skill extraction...") and when ("Use when building a task-local harness, adding eval gates, or extracting a reusable skill from ad-hoc work") with concrete trigger phrases, exactly matching the level-5 anchor; it is not level 4 because the 'when' clause is already explicit and specific.

5 / 5

Trigger Term Quality

Natural phrases like "task-local harness", "eval gates", "extracting a reusable skill", and "dynamic workflow mode" mirror what a user needing this skill would say, but the description misses body synonyms such as "custom loop", "watcher", "crawler", or "control pane", fitting 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

"Claude dynamic workflow mode" and "task-local harness" form a clear niche with distinct triggers, but "other adaptive agent harnesses" and the generic "eval gates" create minor overlap with general workflow/agent-orchestration skills, placing it at 'mostly distinct; minor overlap risk' rather than minimal conflict.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/dynamic-workflow-mode/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.