CtrlK
BlogDocsLog inGet started
Tessl Logo

iikit-core

Initialize an IIKit project, check feature progress, select the active feature, and display the workflow command reference. Use when starting a new project, running init, checking status, switching between features, or looking up available commands and phases.

82

1.74x
Quality

85%

Does it follow best practices?

Impact

82%

1.74x

Average score across 14 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

The canonical home for this skill is tessl-labs/intent-integrity-kit

SKILL.md
Quality
Evals
Security

Quality

Content

85%Scale 1-3

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

This is a strong, well-structured skill that provides clear, actionable guidance for a complex multi-subcommand workflow. The init flow is particularly well-designed with numbered steps, validation checkpoints, and conditional logic. Minor verbosity in some areas (like the working directory note and some explanatory text) prevents a perfect conciseness score, but overall the content is effective and well-organized.

DimensionReasoningScore

Conciseness

The skill is fairly detailed and well-structured, but includes some unnecessary verbosity in places (e.g., explaining what JSON fields mean when Claude can parse them, the lengthy option table for git setup). Some sections could be tightened, but most content earns its place given the complexity of the init workflow.

2 / 3

Actionability

Provides fully executable bash/powershell commands with exact script paths, specific JSON field names to parse, concrete decision trees with prerequisites, and explicit git config commands. The guidance is copy-paste ready throughout.

3 / 3

Workflow Clarity

The init flow has clearly numbered steps (0-7) with explicit validation checkpoints (validate-premise.sh with re-validate loop), auto-skip conditions, prerequisite gates, and error recovery paths. The status and use subcommands also have clear sequenced flows with conditional next-step suggestions.

3 / 3

Progressive Disclosure

Content is well-organized with the main skill file providing an overview and execution flow, while appropriately delegating detailed content to referenced files (prd-seeding.md, help-reference.md, templates). References are one level deep and clearly signaled with relative links.

3 / 3

Total

11

/

12

Passed

Description

85%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured skill description that clearly articulates specific capabilities and includes an explicit 'Use when...' clause with multiple trigger scenarios. The main weakness is that trigger terms are somewhat tied to IIKit-specific jargon, which could limit discoverability for users who don't already know the tool's terminology. Overall, it's a strong description that would perform well in skill selection.

Suggestions

Consider adding more natural language variations users might say, such as 'setup', 'create project', 'help', or 'what commands are available' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Initialize an IIKit project', 'check feature progress', 'select the active feature', and 'display the workflow command reference'. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (initialize project, check progress, select feature, display command reference) and 'when' with an explicit 'Use when...' clause covering starting a new project, running init, checking status, switching features, or looking up commands and phases.

3 / 3

Trigger Term Quality

Includes some natural keywords like 'init', 'status', 'switching between features', 'commands', and 'phases', but 'IIKit' is a niche term and the description lacks common variations a user might say (e.g., 'setup', 'help', 'list commands'). Users unfamiliar with IIKit terminology might not trigger this skill naturally.

2 / 3

Distinctiveness Conflict Risk

The description is clearly scoped to 'IIKit' project management with distinct triggers like 'init', 'feature progress', 'active feature', and 'workflow command reference'. This is a well-defined niche unlikely to conflict with other skills.

3 / 3

Total

11

/

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.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
JaviMontano/mao-iic
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.