agentleFS
Sign inStart free
CliMACliMA/Oceananigans.jl/.claude/skills/build-docs/SKILL.md

build-docs

Skill1.4k starsChanged 9 days agoMITView on GitHub

Build Oceananigans documentation locally with optional fast-build shortcuts

4 other projects use a version of this, 1 of them edited.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 2 mentionsFeb 2026: 2 mentionsMar 2026: 1 mentionApr 2026: 2 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 2 mentionsSep 2026: 1 mentionOct 2026: 7 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the CliMA/Oceananigans.jl repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about CliMA/Oceananigans.jl

The biggest 5 of 48 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 48

Talked about on GitHub, Bluesky and Hacker News (48 times).

On GitHub · 45

40 more on GitHub
  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. NumericalEarth/Breeze.jl★ 9071% same

    Wrote their own version · 3

    1. microsoft/semantic-link-labs★ 594same name
    2. olorehq/olore★ 114same name
    3. NathanForster/claude-commands★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user if they want a full build or a fast build (skipping examples)

    line 12
  2. Very specific:

    Always revert temporary changes to docs/make.jl before committing

    line 35

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

Build Documentation

Build the Oceananigans documentation locally.

Steps

  1. Ask the user if they want a full build or a fast build (skipping examples)
  2. For full build:
    julia --project=docs/ docs/make.jl
  3. For fast build, temporarily modify docs/make.jl:
    • Comment out Literate examples in example_scripts and example_pages
    • Add warnonly = [:cross_references, :example_block, :linkcheck]
    • Comment out GPU-requiring pages
    • Optionally set linkcheck = false, draft = true
    • Run the build
    • Revert all changes to docs/make.jl after building
  4. Serve docs locally for preview:
    using LiveServer
serve(dir="docs/build")
  5. Report any warnings or errors from the build

Notes

  • Fast builds skip examples - use for checking prose and cross-references only
  • Doctests are not part of the docs build; run them with the doctests/doctests test (needs a GPU)
  • Always revert temporary changes to docs/make.jl before committing

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.

Check your setup, free