CtrlK
BlogDocsLog inGet started
Tessl Logo

ipollowork-project-standards

Apply iPolloWork's modern, minimal-change engineering standards when adding features, fixing bugs, refactoring, changing UI, or upgrading dependencies. Use for every implementation task in the iPolloWork repository.

80

Quality

100%

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.

The body is a tight, well-structured standards skill with concrete rules, explicit verification checkpoints, and a single well-signaled reference. It is token-efficient and actionable without over-explaining.

DimensionReasoningScore

Conciseness

Lean imperative prose and bullet lists with no padding or explanation of concepts Claude already knows; every line carries a concrete rule or check.

3 / 3

Actionability

Provides concrete, executable guidance — 'run git diff --check', per-change-type verification checks, and a decision rule — which is actionable without code examples since this is an instruction-only standards skill.

3 / 3

Workflow Clarity

Clear sequence from 'Before changing code' through 'Implementation rules' to 'Verification required' with explicit validation checkpoints and a completion checklist ('inspect the diff, run git diff --check, confirm no unrelated files changed').

3 / 3

Progressive Disclosure

Well-organized sections with a single clearly-signaled, one-level-deep reference to references/architecture.md that exists as a real file; appropriate for a sub-50-line skill.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concise, concrete, and explicitly scoped to the iPolloWork repository with clear what-and-when guidance. It hits the top anchor on all four dimensions with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'adding features, fixing bugs, refactoring, changing UI, or upgrading dependencies' — matching the anchor for several specific concrete actions rather than vague domain naming.

3 / 3

Completeness

Explicitly states what ('apply iPolloWork's modern, minimal-change engineering standards' across named task types) and when ('Use for every implementation task in the iPolloWork repository'), satisfying both halves with an explicit trigger.

3 / 3

Trigger Term Quality

Natural user-facing phrasing covers the common ways a developer would request repo work (features, bugs, refactor, UI, dependencies) plus 'every implementation task', giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped to the iPolloWork repository niche with a distinct, repository-specific trigger, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Devin-AXIS/iPolloWork
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.