CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ecc-contribution-review

Prepare an ECC skill contribution for review by organizing repository, install-surface, cross-harness, validation, security, and commit observations into a local proposal. Use when preparing a skill contribution for review.

Quality

73%

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 ./.cursor/skills/ecc-contribution-review/SKILL.md

The canonical home for this skill is ecc-contribution-review in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

70%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-sequenced, highly actionable compiler workflow with genuine validation and feedback loops, dragged down by repeated non-responsibility disclaimers and dangling documentation references. Consolidating the scope statements and shipping the referenced docs would raise it further.

Suggestions

Consolidate the repeated "the compiler does not X" disclaimers into a single scope statement; the current body restates non-responsibility five or more times.

Ship or remove the docs/WORKFLOW.md and docs/DESIGN.md references — as bundled, two of the three linked documents do not resolve.

Add brief pointers on where to find each observation category (e.g. which manifests or commands reveal install coverage) so steps 1-3 are more directly executable.

DimensionReasoningScore

Conciseness

The body is mostly lean and operational, but the compiler's non-responsibility is restated at least five times ("does not independently inspect Git, files, CI...", "does not execute them", "does not create directories, modify source files, run tests...", "does not prove that supplied claims are true", "never approves a contribution"), which is more than the minor trimming of anchor 4.

3 / 5

Actionability

The core workflow is executable: a copy-paste bash block (mkdir/cp/python3 with arguments), exact exit-code semantics (0 vs 2), and explicit recompile triggers. Minor gaps remain — steps 1-3 are checklists of items to record without how, and the template placeholders are deferred to the bundle.

4 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation (step 6: review every reported contradiction and semantic page fault), a fix-retry feedback loop (step 7: recompile after changes to HEAD, policy, manifests, etc.), and detailed exit-code/error handling guidance ("Inspect the packet and stderr; the exit code alone does not establish whether output exists").

5 / 5

Progressive Disclosure

The body is a concise overview with clearly signaled one-level references, but scored against the actual bundle, two of the three referenced documents (docs/WORKFLOW.md and docs/DESIGN.md) do not exist — only references/contribution-review-contract.md is present — leaving a real navigation gap beyond anchor 4's minor organization issues.

3 / 5

Total

15

/

20

Passed

Description

66%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 a solid, honest niche description with an explicit Use-when clause and clear domain scope, though it is somewhat circular and lacks trigger-term variations. It avoids vague fluff and over-claims.

Suggestions

Add natural trigger variations to the when-clause, e.g. "Use when contributing, submitting, or proposing a skill for review".

Name 1-2 more distinct concrete actions (e.g. "compile a review packet from a template and validate it") instead of one composite organizing action.

Reduce circularity by making the when-clause name concrete situations rather than repeating the skill's title phrase.

DimensionReasoningScore

Specificity

The description names one concrete composite action ("organizing repository, install-surface, cross-harness, validation, security, and commit observations into a local proposal") with an enumeration of observation categories, but does not list several distinct actions as anchor 4 requires; it exceeds anchor 2's generic minimal action.

3 / 5

Completeness

Both "what" (organizing six categories of observations into a local proposal) and "when" ("Use when preparing a skill contribution for review") are explicitly present, but the when-clause merely restates the task without additional concrete trigger phrases, so it does not reach anchor 5.

4 / 5

Trigger Term Quality

Relevant keywords like "skill contribution", "review", and "ECC" are present, but common variations and synonyms a user might say ("submit a skill", "propose", "pull request") are missing, matching anchor 3 rather than the fuller coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The ECC skill-contribution review niche is highly specific with a distinct trigger phrase ("preparing a skill contribution for review"), giving minimal overlap risk with general document, code-review, or PDF-type skills.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 2 possibly missing (docs/DESIGN.md, docs/WORKFLOW.md)

Warning

Total

14

/

16

Passed

Repository

affaan-m/ECC

Path

.cursor/skills/ecc-contribution-review/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.