CtrlK
BlogDocsLog inGet started
Tessl Logo

macports-natron-upgrade

Upgrade the local Natron MacPorts portfile overlay against upstream MacPorts, and build Natron into a macOS arm64 DMG. Use when asked to update/upgrade the Natron MacPorts ports, run check.sh, reintegrate upstream Portfile changes, resolve failing Natron patchfiles after a MacPorts sync, regenerate Portfile.patch files, or build Natron / produce a DMG via tools/jenkins/launchBuildMain.sh. Enforces that lang/libomp stays pinned.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

A highly actionable, well-sequenced workflow skill with strong validation checkpoints and a verified bundle script, weakened mainly by verbosity in the compiler-pin history and a monolithic structure that keeps build/DMG detail inline. Tightening the prose and offloading large subsections to reference files would raise it further.

Suggestions

Condense the Compiler pin section: move the time-sensitive version numbers (clang-mp-17, macOS 26 / Darwin 25, libomp 11.1.0) and the legacy-vs-current reasoning into a dedicated 'Pins' reference or a clearly marked deprecated/old-patterns block so the main workflow stays lean.

Move the 'Building Natron (produce a DMG)' section and its long prerequisites list into a separate reference file (e.g. references/build-dmg.md) and keep a one-line pointer in SKILL.md to improve progressive disclosure.

Consolidate the libomp constraint, which is restated across 'CRITICAL constraint', Step 3, Step 7, and 'Common mistakes' — state the rationale once and cross-reference it to reduce repetition.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific commands and avoids explaining concepts Claude already knows, but the Compiler pin section's legacy/current historical reasoning ("clang_version=16 (11 on 10.6) for two reasons…") and inline time-sensitive version numbers (clang-mp-17, macOS 26, libomp 11.1.0) could be tightened; not a 3 because these are not isolated in a dedicated deprecated/pins section and some prose is restated.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands throughout ("sudo port selfupdate", "./check.sh", "cp "$ports/$P/Portfile" "$P/Portfile.orig"", the per-port upgrade loop, the clang verification snippet, the nohup launchBuildMain.sh invocation) plus a Quick reference table with concrete paths; not a 2 because there is no pseudocode or missing key details.

3 / 3

Workflow Clarity

Steps 0–7 are clearly sequenced with a Mermaid loop diagram and explicit validation checkpoints ("Re-run ./check.sh… until it reports nothing obsolete", "Re-run ./sync.sh until portindex parses all ports", "Loop Steps 5–6 until… no failures") including a fix-and-retry feedback loop for the batch upgrade; not a 2 because validation is present for the batch operation rather than missing.

3 / 3

Progressive Disclosure

Sections are well-organized with a Quick reference table and the one bundle reference (scripts/regen-portfile-patches.sh, verified to exist) is clearly signaled and one level deep, but the doc is largely monolithic with the build/DMG and compiler-pin detail kept inline rather than split into reference files; not a 3 because content that could be separate is not split, and not a 1 because there are no nested references and navigation is clear.

2 / 3

Total

10

/

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.

A strong description: it states concrete capabilities, includes an explicit "Use when…" trigger list covering natural user phrasings, and occupies a distinct Natron/MacPorts niche in third-person voice. No meaningful weaknesses to address.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Upgrade the local Natron MacPorts portfile overlay against upstream MacPorts", "build Natron into a macOS arm64 DMG", "reintegrate upstream Portfile changes, resolve failing Natron patchfiles", "regenerate Portfile.patch files", "Enforces that lang/libomp stays pinned" — matching the multiple-specific-actions anchor; not a 2 because it goes well beyond naming a domain plus a few actions.

3 / 3

Completeness

Explicitly answers what ("Upgrade the local Natron MacPorts portfile overlay… and build Natron into a macOS arm64 DMG") and when (the "Use when…" clause with explicit triggers), matching the both-what-and-when anchor; not a 2 because the when is explicit, not merely implied.

3 / 3

Trigger Term Quality

The "Use when asked to update/upgrade the Natron MacPorts ports, run check.sh, reintegrate upstream Portfile changes, resolve failing Natron patchfiles after a MacPorts sync, regenerate Portfile.patch files, or build Natron / produce a DMG" clause gives good coverage of the natural phrases a Natron maintainer would say; not a 2 because it spans many variations rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

The Natron/MacPorts portfile-overlay + arm64 DMG niche with lang/libomp pinning and tools/jenkins/launchBuildMain.sh references is highly specific and unlikely to trigger for another skill; not a 2 because it does not overlap with generic skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
NatronGitHub/Natron
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.