Source profileQuality 67/100

nexu-io/open-design/skills/field-notes-editorial-template/SKILL.md

field-notes-editorial-template

Editorial "Field Notes" report template with soft paper background, serif hero typography, rounded pastel insight cards, and a retention chart panel. Use when users ask for a premium magazine-style business report, board memo one-pager, or elegant data storytelling layout.

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

Decision brief

What it does—and where it fits

Produce a premium editorial data report in a single self-contained HTML file.

Best for

  • Use when users ask for a premium magazine-style business report, board memo one-pager, or elegant data storytelling layout.

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/field-notes-editorial-template"
Safe inspection promptEditorial

Inspect the Agent Skill "field-notes-editorial-template" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/skills/field-notes-editorial-template/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 active DESIGN.md and map palette/typography to root CSS variables. 2. Copy assets/template.html to index.html as the working artifact. 3. Keep the editorial frame language: - paper-like background and subtle vignette - serif display headlines plus clean sans-serif body c…

    Read active DESIGN.md and map palette/typography to root CSS variables.Copy assets/template.html to index.html as the working artifact.Keep the editorial frame language:
  2. 02

    Resource map

    Review the “Resource map” section in the pinned source before continuing.

    Review and apply the “Resource map” source section.
  3. 03

    Output contract

    One short orientation sentence, then:

    One short orientation sentence, then:

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 score67/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars82,073SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

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

Field Notes Editorial Template

Produce a premium editorial data report in a single self-contained HTML file.

Resource map

field-notes-editorial-template/
├── SKILL.md
├── assets/
│   └── template.html
├── references/
│   └── checklist.md
└── example.html

Workflow

  1. Read active DESIGN.md and map palette/typography to root CSS variables.
  2. Copy assets/template.html to index.html as the working artifact.
  3. Keep the editorial frame language:
    • paper-like background and subtle vignette
    • serif display headlines plus clean sans-serif body copy
    • rounded pastel metric / insight cards
    • chart panel with legend and axis labels
  4. Keep interactions lightweight and presentation-safe:
    • page view switcher (metrics / insights / retention)
    • number count-up animation for key metrics
    • chart line reveal animation
  5. Use honest placeholders ( or neutral labels) where data is unknown.
  6. Validate against references/checklist.md before emitting.

Output contract

One short orientation sentence, then:

<artifact identifier="field-notes-editorial" type="text/html" title="Field Notes Editorial Report">
<!doctype html>
<html>...</html>
</artifact>

Alternatives

Compare before choosing