neko-plugin

Work on N.E.K.O plugins end to end. Use when the user asks to create, modify, review, run, debug, inspect, document, validate, package, or reason about N.E.K.O plugins, plugin.toml, plugin SDK usage, plugin UI surfaces, plugin CLI tooling, plugin runtime behavior, or plugin system contracts.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 content is a well-structured entry point: concise, actionable, and properly deferential to bundled references. Workflows are sequenced with validation steps, and all referenced files exist at one level of depth, making navigation straightforward.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining basic concepts; every section earns its place with no padding.	3 / 3
Actionability	Provides concrete, executable guidance — `uv run neko-plugin init ...`, `uv run neko-plugin check <plugin_id\|plugin_path>`, specific public SDK facades (`plugin.sdk.plugin`, `plugin.sdk.extension`, `plugin.sdk.adapter`) — rather than vague direction.	3 / 3
Workflow Clarity	Multi-step workflows (Create, Modify, Debug, Review, Escalate) are explicitly numbered with validation checkpoints such as "Validate with the focused checks" and "Run the narrowest plugin-facing check or test that covers the change."	3 / 3
Progressive Disclosure	The body is a navigable overview with a Reference Map pointing to eight real, one-level-deep reference files (all verified to exist in ./references/); detailed material is appropriately split out of the main file.	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 yet comprehensive: it states a clear capability set and gives explicit, varied trigger terms anchored in the N.E.K.O plugin domain. It cleanly answers both what and when with minimal risk of skill conflicts.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions ("create, modify, review, run, debug, inspect, document, validate, package, or reason about") rather than vague language, matching the top anchor.	3 / 3
Completeness	Explicitly answers both what (the enumerated plugin actions) and when ("Use when the user asks to create, modify, review, run, debug, inspect, document, validate, package, or reason about ..."), with an explicit Use-when clause.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — "plugin.toml", "plugin SDK usage", "plugin UI surfaces", "plugin CLI tooling", "plugin runtime behavior" — with good breadth and variation.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to the N.E.K.O plugin niche with domain-specific trigger objects, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Project-N-E-K-O/N.E.K.O
Path: .agent/skills/neko-plugin/SKILL.md
Commit: c6f1797

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.