CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentic-contribution-skill

Interactive skill creation and import with automated validation and marketplace compliance. Use when: - "Create a new skill" - "Import an existing skill" - "Create a new agent plugin" - "Add skill to <plugin>" - "Build skill for <rh-product>" - User mentions "skill builder", "contribute", "new skill", "import skill", or "new plugin" Two modes: create from scratch or import existing SKILL.md. Guides through discovery, definition, generation, and validation. Enforces SKILL_DESIGN_PRINCIPLES.md and agentskills.io spec.

Quality

84%

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

81%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 highly actionable, well-sequenced interactive workflow with strong validation feedback loops and a clean bundle reference. Its weakness is repetition: redundant reassurance statements and a quick-example section that restates the workflow inflate the token budget near the 500-line limit.

Suggestions

Cut repeated statements ("already consulted in Phase 3", "quality is the priority, not speed" variants, the iteration-note restatements) — say each once and reference it.

Remove or shrink the Quick Example section that restates the Phase 0-6 workflow already documented in Workflow, pointing to references/examples.md instead.

Move the Phase 1-Import keyword-to-plugin table and Issue 7 walkthrough detail into references/ to bring the main file well under the 500-line limit and raise the progressive-disclosure score.

DimensionReasoningScore

Conciseness

Mostly procedural and efficient — no explanations of concepts Claude already knows — but padded with repetition: "already consulted in Phase 3" restated across Phases 3-5, "quality is the priority, not speed" stated multiple ways, and an Example Usage section that restates the Phase 0-6 workflow. More than minor trimming is possible, so below the 4 anchor.

3 / 5

Actionability

Fully executable throughout: copy-paste-ready prerequisite checks ("test -d .git && echo ..."), validation commands ("uv run python scripts/validate_skills_tier1.py <plugin>/skills/<skill-name>/SKILL.md"), report templates, git credential fixes, and exact question scripts for each discovery/definition step. Covers the common create and import cases.

5 / 5

Workflow Clarity

Phases 0-8 are clearly sequenced with explicit validation checkpoints (Phase 5), a full feedback loop (analyze errors → apply fixes → re-validate → "Repeat until ✅ PASSED"), and confirmation gates before every risky git operation. Matches the 5 anchor with feedback loops and checklists.

5 / 5

Progressive Disclosure

Well-signaled, one-level-deep reference to references/examples.md (verified to exist) plus clearly sectioned phases. Not 5: the ~445-line body sits near the 500-line limit with content (the import keyword table, color mapping table, and issue walkthroughs) that could be split into references/, and only one bundle reference file exists.

4 / 5

Total

17

/

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 that explicitly states what the skill does and when to use it, with concrete, natural trigger phrases. The main risks are minor: the broad "contribute" trigger could over-fire on general contribution questions, and a few capabilities are unlisted.

Suggestions

Drop or narrow the "contribute" trigger (e.g., "contribute a skill") since general contribution questions are explicitly out of scope for this skill.

Mention the guided git workflow (branch/commit/PR with user confirmation) to round out the capability list currently missing from the "what" statement.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("skill creation and import with automated validation and marketplace compliance", "Guides through discovery, definition, generation, and validation", "Enforces SKILL_DESIGN_PRINCIPLES.md and agentskills.io spec"). Minor gaps: the git workflow, plugin scaffolding, and AGENTS.md routing capabilities covered in the body are absent from the description.

4 / 5

Completeness

Clearly answers both "what" (interactive creation/import, two modes, guided discovery-through-validation pipeline, marketplace compliance) and "when" via an explicit "Use when:" clause with concrete quoted trigger phrases. Matches the 5 anchor exactly.

5 / 5

Trigger Term Quality

Good coverage of natural user phrases ("Create a new skill", "Import an existing skill", "skill builder", "import skill", "new plugin") including synonyms. Not 5: a few natural phrasings are missing ("write a skill", "skill template") and "contribute" is broad enough to match general contribution requests.

4 / 5

Distinctiveness Conflict Risk

Clear niche (skill and agent-plugin authoring for Red Hat products) with distinct triggers, but "contribute" and "new plugin" create minor overlap risk with general contribution or plugin-management skills. Mostly distinct, not fully minimal-conflict.

4 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing, 4 suspicious

Warning

referenced_paths_exist

Referenced path issues: 14 missing, 2 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

.claude/skills/agentic-contribution-skill/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.