CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research

Research prior art and external editor evidence for any Plate or Plite feature, picking the gap most likely to change a decision; compare external editor architectures through a strict source inventory; harvest portable tests from external editors; and maintain the compiled research layer. Use it before writing, moving or compiling any page under docs/research, including lessons compiled from retired internal docs.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 dense, highly actionable skill body: concrete commands, schemas, thresholds, and validation loops throughout, with the audit and harvest sub-workflows correctly pushed to real reference files. Its main cost is density — long multi-clause paragraphs and inline rule detail (gap taxonomy, ledger parsing) that could be tightened or extracted, plus one raw date outside a deprecated section.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout — no padding, no explanations of known concepts — with dense, information-bearing prose. It misses the level-5 anchor because several 100+ word single-paragraph rule dumps (the seven-gap taxonomy, the ledger-reading rules), a run-on "What is known" step nesting five file-reading instructions, and a bare time-sensitive date "(2026-10-06)" outside any deprecated section could be tightened or split out.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands with argument shapes ("node tooling/scripts/review-ledger.mjs due", "pnpm kb discover <area>"), explicit TSV artifact schemas with column names, a concrete promotion threshold ("impact + novelty + applicability + proofability - risk >= 7"), shard batch sizes, and A–D evidence grades. This matches the level-5 anchor — specific commands and examples covering the common cases.

5 / 5

Workflow Clarity

The pipeline is stated up front ("pick -> question -> registry -> queries -> leads -> read log -> score -> promote") and each phase carries explicit ordering markers ("before the first search", "after every shard", "Before the run ends") plus stop rules. Validation checkpoints and feedback loops are present — "run the helper's check command" after ledger changes, rejected leads with reopen conditions, and per-corpus dispositions with next actions — matching the level-5 anchor.

5 / 5

Progressive Disclosure

The two heavy sub-workflows are properly externalized to real, well-signaled one-level-deep references ([editor audit](./references/editor-audit.md), [test harvest](./references/test-harvest.md)), each linked from the mode that needs it. It sits at level 4 rather than 5 because the main body still inlines substantial detail that could be split out — roughly 30 lines of ledger-parsing rules in "Reading research ledgers" and the seven inline gap-type definitions.

4 / 5

Total

18

/

20

Passed

Description

92%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 voice, four concrete capability statements, and an explicit use-when clause tied to the docs/research trigger surface. The only weakness is modest synonym coverage for how users might phrase a research or audit request.

DimensionReasoningScore

Specificity

The description lists four concrete actions — "Research prior art and external editor evidence… picking the gap most likely to change a decision", "compare external editor architectures through a strict source inventory", "harvest portable tests from external editors", "maintain the compiled research layer" — covering all of the skill's primary modes. It matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage) rather than level 4 because no named capability is left out.

5 / 5

Completeness

Both halves are explicit: the what is the list of concrete research/audit/harvest/maintain actions, and the when is "Use it before writing, moving or compiling any page under docs/research, including lessons compiled from retired internal docs". This clearly matches the level-5 anchor — explicit what and when with concrete trigger phrases — and not level 4, where the when would be less specific.

5 / 5

Trigger Term Quality

Natural trigger terms are present ("prior art", "research", "external editor", "harvest", "tests", "docs/research", "Plate", "Plite"), giving good keyword coverage. It falls short of the level-5 anchor because a few natural phrasings users would say are missing, such as "audit", "investigate", or "how do other editors handle X".

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche through project-specific naming (Plate/Plite features, external editor architectures, the docs/research compiled layer), so it is unlikely to trigger for an unrelated skill. It matches the level-5 anchor (clear niche, distinct triggers, minimal conflict risk) rather than level 4, which requires some overlap risk with closely related skills.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

Total

13

/

16

Passed

Repository

udecode/plate

Path

.agents/skills/research/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.