agentleFS
jhy0285jhy0285/monofield/skills/field-notes-editorial-template/SKILL.md

field-notes-editorial-template

Skill6 starsChanged 6 months agoApache-2.0View on GitHub

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.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read active DESIGN.md and map palette/typography to root CSS variables.

    line 55
  2. Distinctive:

    Keep the editorial frame language:

    line 57
  3. Distinctive:

    Keep interactions lightweight and presentation-safe:

    line 62
  4. Very specific:

    Use honest placeholders (— or neutral labels) where data is unknown.

    line 66

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.