CtrlK
BlogDocsLog inGet started
Tessl Logo

project-standards-reviewer

Always-on code-review persona. Audits changes against the project's own CLAUDE.md and AGENTS.md standards -- frontmatter rules, reference inclusion, naming conventions, cross-platform portability, and tool selection policies.

67

Quality

83%

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

100%

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

A lean, highly actionable instruction-only audit persona with clear workflow checkpoints and a self-contained, well-organized structure; it earns top marks across all content dimensions.

DimensionReasoningScore

Conciseness

The body is dense and task-focused with no explanation of concepts Claude already knows; its length reflects justified coverage of distinct violation categories rather than padding, and punchy gates like 'Drop it.' earn their tokens.

3 / 3

Actionability

Provides concrete numbered discovery steps, specific violation examples (e.g. 'TodoWrite instead of TaskCreate/TaskUpdate'), explicit evidence requirements, and a copy-paste JSON output template.

3 / 3

Workflow Clarity

Clear sequence (discover standards, match rules to file types, hunt violations, calibrate confidence) with explicit checkpoints: the 0.60 confidence suppression threshold and the rule-plus-violation evidence gate.

3 / 3

Progressive Disclosure

Self-contained skill with no bundle files, organized into well-signaled sections (Standards discovery, What you're hunting for, Confidence calibration, Evidence requirements, Output format); per the guidelines a well-organized single-file skill scores 3.

3 / 3

Total

12

/

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.

A specific, distinctive description that names concrete audit capabilities, but it lacks an explicit 'Use when...' trigger clause and leans on technical category labels rather than natural user-facing trigger terms.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when reviewing changes that touch SKILL.md, agent files, or code governed by project CLAUDE.md/AGENTS.md standards.', to raise completeness above 2.

Surface natural user-facing trigger terms ('review my changes', 'check standards compliance', 'lint my skills', 'code review') alongside the technical category list to improve trigger term quality.

Lead with the distinctive standards-auditing niche rather than the generic 'Always-on code-review persona' framing to further reduce overlap with general code-review skills.

DimensionReasoningScore

Specificity

Enumerates five concrete audit categories ('frontmatter rules, reference inclusion, naming conventions, cross-platform portability, and tool selection policies') rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It clearly states what the skill does but the 'when' is only implied via 'Always-on'; there is no explicit 'Use when...' clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes some natural terms ('code-review', 'CLAUDE.md', 'AGENTS.md') but the remaining phrases describe what it checks rather than user-facing triggers, and 'Always-on' is an activation mode, not a natural trigger phrase.

2 / 3

Distinctiveness Conflict Risk

The CLAUDE.md/AGENTS.md standards-auditing niche is a clear, distinct domain unlikely to trigger for unrelated skills, despite the slightly generic 'code-review persona' lead.

3 / 3

Total

10

/

12

Passed

Validation

75%

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

Validation12 / 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

relative_links

Relative link issues: 2 missing

Warning

Total

12

/

16

Passed

Repository
udecode/plate
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.