Source profileQuality 77/100

nexu-io/open-design/skills/release-notes-one-pager/SKILL.md

release-notes-one-pager

Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note. Writes explicit "None" style sections whenever the user does not provide details.

Source repository stars
82,073
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Produce a single-page release notes document in HTML.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/nexu-io/open-design --skill "skills/release-notes-one-pager"
    Safe inspection promptEditorial

    Inspect the Agent Skill "release-notes-one-pager" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/skills/release-notes-one-pager/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Workflow

      1. Read assets/template.html. 2. Read references/layouts.md. 3. Read active DESIGN.md and map it to the six :root variables.

      Read assets/template.html.Read references/layouts.md.Read active DESIGN.md and map it to the six :root variables.
    2. 02

      Step 0 — Pre-flight

      1. Read assets/template.html. 2. Read references/layouts.md. 3. Read active DESIGN.md and map it to the six :root variables.

      Read assets/template.html.Read references/layouts.md.Read active DESIGN.md and map it to the six :root variables.
    3. 03

      Step 1 — Start from the shared seed

      Copy assets/template.html to project index.html.

      topnav logo texttopnav link labels (destinations are pre-wired to added, fixed, upgrade-note)topnav CTA label and href destination, or omit the topnav CTA entirely if no real destination exists
    4. 04

      Step 2 — Build release-note structure

      Inside , compose this section order:

      Hero (Layout 1 or 2): version, date, one-sentence summary.Added (use Layout 7 log-list; section root must include id="added").Fixed (use Layout 7 log-list; section root must include id="fixed").

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score77/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars82,073SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    nexu-io/open-design
    Skill path
    skills/release-notes-one-pager/SKILL.md
    Commit
    89d6d4ef21baf80f871595abdf6f7de6e941dd44
    License
    Apache-2.0
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Release Notes One-Pager Skill

    Produce a single-page release notes document in HTML.

    Resource map

    release-notes-one-pager/
├── SKILL.md                    ← this file
├── example.html                ← quality bar and style reference
├── assets/
│   └── template.html           ← local seed file to copy to project index.html
└── references/
    ├── checklist.md            ← P0 / P1 / P2 gates
    └── layouts.md              ← local section skeletons

    Do not write CSS from scratch unless the user explicitly asks for a bespoke structure.

    Workflow

    Step 0 — Pre-flight

    1. Read assets/template.html.
    2. Read references/layouts.md.
    3. Read active DESIGN.md and map it to the six :root variables.

    Step 1 — Start from the shared seed

    Copy assets/template.html to project index.html.

    Update:

    • <title>
    • topnav logo text
    • topnav link labels (destinations are pre-wired to #added, #fixed, #upgrade-note)
    • topnav CTA label and href destination, or omit the topnav CTA entirely if no real destination exists
    • ensure the topnav link targets exist by adding matching section id attributes

    Step 2 — Build release-note structure

    Inside <main id="content">, compose this section order:

    1. Hero (Layout 1 or 2): version, date, one-sentence summary.
    2. Added (use Layout 7 log-list; section root must include id="added").
    3. Fixed (use Layout 7 log-list; section root must include id="fixed").
    4. Breaking changes (use Layout 7 log-list, or one row explicitly saying "None"; section root must include id="breaking-changes").
    5. Known issues (Layout 7 or card list; section root must include id="known-issues").
    6. Upgrade note (short steps list or explicit no-action statement; section root must include id="upgrade-note").
    7. Closing CTA strip (Layout 6).

    For every CTA in the emitted HTML (topnav, hero, closing strip), replace both the visible label and the href destination with real, safe values. If no real destination is available, omit the CTA entirely—do not use a placeholder such as href="#", a misleading page-anchor, or REPLACE_WITH_REAL_URL. Hero CTAs are optional; only add them when real destinations exist.

    Step 3 — Honesty rules for missing details

    If the user does not provide details, do not invent them. Write explicit placeholders:

    • Summary: No summary provided.
    • Added: No additions provided
    • Fixed: No fixes provided
    • Breaking changes: None
    • Known issues: None reported
    • Upgrade note: No upgrade actions required based on provided information

    If release version or date is missing, use — and label the field rather than guessing.

    Step 4 — Self-check

    Run references/checklist.md. Every P0 must pass.

    Step 5 — Emit artifact

    Wrap output as:

    <artifact identifier="release-notes-one-pager" type="text/html" title="Release Notes">
<!doctype html>
<html>...</html>
</artifact>

    One sentence before the artifact. Nothing after </artifact>.

    Alternatives

    Compare before choosing

    Computed 95234,327

    affaan-m/ECC

    mle-workflow

    Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.

    2026-07-270 platforms
    Computed 9531,966

    K-Dense-AI/scientific-agent-skills

    simpy

    Build, inspect, test, and analyze bounded process-based discrete-event simulations with SimPy, including events, resources, interrupts, monitoring, replications, warm-up, and reproducible output analysis.

    2026-07-280 platforms
    Computed 95165

    JasonColapietro/suede-creator-skills

    suede-code-grader

    Give a blunt A-F ship grade for a code change across correctness, security, data, UX, verification, and deploy readiness. Use for a grade, not a findings review.

    2026-07-280 platforms
    Computed 957

    event4u-app/agent-config

    terragrunt

    Use when working with Terragrunt — DRY multi-env configs, module dependencies, remote state orchestration — even when the user just says 'deploy this to staging and prod' without naming Terragrunt.

    2026-07-280 platforms