editor-harvest-plan

Turn an editor-test-harvester report into one lane-specific execution plan, e.g. process every Slate v2 candidate from a harvest through slate-plan without executing implementation.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/editor-harvest-plan/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a well-sequenced, validated workflow, but it is a long monolithic document with policy repetition and no progressive disclosure into bundle files, leaving conciseness and progressive disclosure at the mid level.

Suggestions

Dedupe the behavior-only/fresh-invariant and license-provenance rules so they live in one section (e.g., Hard Policy) and are referenced rather than restated in Workflow, Action Values, and Confidence Score.

Move the Lane Registry and Confidence Score detail tables into a references/ file referenced one level deep to improve progressive disclosure and shorten the overview.

Tighten the Issue And Claim Accounting boilerplate block, which is largely fixed text that could be referenced or templated.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly domain-specific rather than explaining known concepts, but it repeats policy (behavior-only/fresh-invariant and license-provenance rules appear in Hard Policy, Workflow, Action Values, and Confidence Score) and could be tightened, fitting the score-2 anchor of mostly efficient with some unnecessary repetition.	2 / 3
Actionability	It gives concrete executable commands (create-goal-scratchpad.mjs with --template editor-harvest-plan, check-complete.mjs, specific rg verification strings) and exact file-path patterns, matching the score-3 anchor of fully executable commands and copy-paste-ready examples.	3 / 3
Workflow Clarity	The 14-step Workflow is explicitly sequenced with validation checkpoints (threshold checks, check-complete.mjs, pending/blocked/done state transitions, confidence-score caps), matching the score-3 anchor of a clear sequence with explicit validation and feedback loops.	3 / 3
Progressive Disclosure	No bundle files exist in references/scripts/assets, so the skill is a single ~340-line monolithic SKILL.md with inline content (lane registry, confidence table, full policy) that could be split out, fitting the score-2 anchor of some structure but content that should be separate is inline.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and clearly distinct within its niche, but it lacks an explicit "Use when..." trigger clause and leans on specialized jargon rather than natural user phrasing, capping completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when the user wants one lane from a harvester report turned into a plan") to lift completeness to 3.

Include natural-language trigger variations users might actually say ("plan the Slate tests from this harvest", "route this harvester result") alongside the technical terms.

Keep the concrete actions but consider trimming the inline example so the trigger guidance is not crowded out.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions: "Turn an editor-test-harvester report into one lane-specific execution plan" and "process every Slate v2 candidate from a harvest through slate-plan without executing implementation," matching the score-3 anchor of listing several specific concrete actions.	3 / 3
Completeness	It clearly answers "what" (turn a report into a lane-specific plan) but "when" is only implied via the "e.g." clause with no "Use when..." trigger guidance, so per the guideline a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	It surfaces domain terms a user in this niche would say ("Slate v2", "harvest", "editor-test-harvester", "slate-plan"), but these are specialized jargon with no common phrasing variations, fitting the score-2 anchor of some relevant keywords but missing common variations.	2 / 3
Distinctiveness Conflict Risk	The niche is sharply defined by "editor-test-harvester report", "lane-specific execution plan", and "slate-plan," making it unlikely to trigger for unrelated skills, matching the score-3 anchor of a clear distinct niche.	3 / 3
	Total	10 / 12 Passed

Validation

75%

Warnings & errors only

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

Validation — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	12 / 16 Passed

Repository: udecode/plate
Path: .agents/skills/editor-harvest-plan/SKILL.md
Commit: 45116fd

Reviewed: about 15 hours ago

Table of Contents

Discovery Implementation Validation

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.