natron-maintainer

Domain knowledge for working on the Natron compositor's own C++ source code (Engine/Gui/HostSupport). Use when navigating, fixing, or extending the Natron codebase, doing Qt5/Qt6 work, building Natron, building its Sphinx docs, or triaging its GitHub issues.

Quality

93%

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

87%Weight 40%Scale 1-3

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 lean, actionable maintainer reference with executable commands and well-organized sections that defer depth to one-level-deep in-repo guide chapters. Its main weakness is workflow clarity: the build/test and triage flows lack explicit validation checkpoints or error-recovery feedback loops.

Suggestions

Add explicit validation/feedback checkpoints to the build workflow, e.g. after `ctest --test-dir build` add a step: 'If tests fail, fix and re-run before proceeding.'

Turn the Issue Triage Method into a short numbered checklist with a verify step (e.g. re-confirm a P0 is reproducible before prioritizing) rather than a prose description.

For the Qt 6 migration list, add a small verification step (e.g. 'build with -DNATRON_QT6=ON and run ctest after each item') so progress can be checked per-task.

Dimension	Reasoning	Score
Conciseness	The body is dense and high-signal — naming-convention tables, terse idioms, and copy-paste commands assume Claude's competence and avoid explaining basic concepts, so every section earns its tokens rather than padding.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands (cmake/ctest, astyle, sphinx-build, curl) plus concrete naming tables and idioms, matching the anchor for executable code and specific examples rather than vague direction.	3 / 3
Workflow Clarity	Build/test and issue-triage are sequenced, but neither includes explicit validation checkpoints or feedback loops (e.g., 'if ctest fails, fix and rerun'), fitting the 'sequence present but checkpoints missing or implicit' anchor and falling short of the explicit-validation level.	2 / 3
Progressive Disclosure	The body is explicitly 'the quick map' and defers depth to well-signaled one-level-deep in-repo references ('authoritative long-form reference is the in-repo Maintainer Guide', 'Full plan: ...qt6-migration.rst', 'Full analysis: ...issue-triage.rst'); no bundle files exist, so structure is judged on the body's organization, which is clear and easy to navigate.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%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.

The description is concise, concrete, and answers both what it does and when to use it with an explicit 'Use when' clause. It targets a distinct niche with natural trigger terms a maintainer would actually say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('navigating, fixing, or extending the Natron codebase, doing Qt5/Qt6 work, building Natron, building its Sphinx docs, or triaging its GitHub issues'), matching the anchor for listing multiple specific concrete actions rather than naming only some.	3 / 3
Completeness	Clearly states what ('Domain knowledge for working on the Natron compositor's own C++ source code') and an explicit 'Use when ...' clause with concrete triggers, satisfying both what and when.	3 / 3
Trigger Term Quality	Natural terms a maintainer would say ('Natron codebase', 'Qt5/Qt6', 'Sphinx docs', 'GitHub issues') give good coverage; the parenthetical 'Engine/Gui/HostSupport' is mild jargon but not the primary triggers, so it stays above the 'missing common variations' level.	3 / 3
Distinctiveness Conflict Risk	Highly niche focus on the Natron compositor's own C++ source with distinct triggers makes it unlikely to fire for an unrelated skill, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NatronGitHub/Natron
Path: skills/natron-maintainer/SKILL.md
Commit: 3763d80

Reviewed: ~1 month 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.