agentleFS
markoblogomarkoblogo/abvx-agent-skills/skills/editorial-surface/SKILL.md

editorial-surface

Skill16 starsChanged 5 months agoMITView on GitHub

Shape editorial and reading-first surfaces with strong hierarchy, readable measure, and disciplined media rhythm. Use for articles, guides, books, blog indexes, featured/recent cards, and other longform or text-heavy public surfaces.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat reading experience as a product requirement, not decorative polish.

    line 13
  2. Distinctive:

    Use this when the surface is text-first and the common failure mode is bad hierarchy, empty cards, oversized hero treatments, weak excerpt …

    line 15
  3. Distinctive:

    not automatically adjacent to cover art if that creates a media wall.

    line 55
  4. Distinctive:

    not after the entire article if it belongs near the core narrative.

    line 56
  5. Distinctive:

    Verify desktop and mobile reading comfort before calling the change ready.

    line 57
  6. Distinctive:

    Do not rewrite owner-approved article body unless explicitly asked.

    line 72
  7. Distinctive:

    Do not turn editorial pages into generic marketing pages.

    line 73
  8. Distinctive:

    Do not add decorative imagery to cover for weak hierarchy.

    line 74
  9. Distinctive:

    Do not shrink content density so far that text-first surfaces become empty.

    line 75
  10. Distinctive:

    Do not imitate Medium or Substack blindly when the project has its own identity.

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Editorial Surface

Treat reading experience as a product requirement, not decorative polish.

Use this when the surface is text-first and the common failure mode is bad hierarchy, empty cards, oversized hero treatments, weak excerpt logic, or unreadable body rhythm.

Best Fit

  • article pages;
  • blog and writing indexes;
  • guide pages;
  • book and booklet landing sections;
  • featured and recent content cards;
  • mixed text/media editorial layouts.

Design Priorities

  • title, deck, metadata, and body must read as one system;
  • body measure and paragraph rhythm win over decorative hero treatment;
  • cards should carry the right amount of information for their role;
  • media should support reading, not interrupt it;
  • text-only surfaces should still feel intentionally composed.

Workflow

  1. Identify the content role:
    • index, featured card, recent card, article page, guide, or mixed editorial section.
  2. State the reading job:
    • skim, choose, commit, or read deeply.
  3. Check the hierarchy:
    • label/source/date;
    • title;
    • deck/excerpt;
    • body;
    • supporting media;
    • actions and related links.
  4. Fix the common structural failures first:
    • oversized title block;
    • empty right side on text-only featured cards;
    • recent cards with dead space instead of useful excerpt;
    • metadata too faint to scan;
    • body too light, narrow, or long-line;
    • video or external resources placed without narrative rhythm.
  5. For mixed media, place media where it helps comprehension:
    • not automatically adjacent to cover art if that creates a media wall;
    • not after the entire article if it belongs near the core narrative.
  6. Verify desktop and mobile reading comfort before calling the change ready.

Output Shape

Return:

  • content role
  • reading job
  • hierarchy fixes
  • excerpt rule
  • media placement rule
  • desktop/mobile reading checks

Guardrails

  • Do not rewrite owner-approved article body unless explicitly asked.
  • Do not turn editorial pages into generic marketing pages.
  • Do not add decorative imagery to cover for weak hierarchy.
  • Do not shrink content density so far that text-first surfaces become empty.
  • Do not imitate Medium or Substack blindly when the project has its own identity.

Final Report

Include:

  • the content role handled;
  • the main hierarchy correction;
  • the excerpt or media rule applied;
  • desktop/mobile reading evidence;
  • any remaining issue that still needs anti-slop-review or browser-verification.

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.