agentleFS
Sign inStart free
pavelkorolevxyzpavelkorolevxyz/craft/SKILL.md

craft

Skill4 starsChanged 42 days agoMITView on GitHub

Use Craft for standalone HTML pages and slide decks.

10 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

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 6

    Distinctive

    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:

    Read the shared identity rules and the build and check workflow.

    line 9
  2. Distinctive:

    Follow only the chosen branch below.

    line 10
  3. Distinctive:

    Before HTML, read the talk outline and choosing a layout, then the visual language and the mechanics.

    line 14
  4. Distinctive:

    Read the page layout, the visual language and the component index.

    line 28
  5. Distinctive:

    If the material will be printed or saved as PDF, read print.

    line 30
  6. Distinctive:

    Read the extension rules. Level theory, catalog internals and releases are not needed for a normal build.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 9 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

Craft

  1. Pick the format. A talk or presentation uses slides. A page to read or operate uses interface. If the format is unclear, read the format map.
  2. Read the shared identity rules and the build and check workflow. If the material is in Russian, also read material in Russian.
  3. Follow only the chosen branch below. Open a reference from the "by content" list only if the material has that content. Do not read the catalog or references ahead of time.

Slides

Before HTML, read the talk outline and choosing a layout, then the visual language and the mechanics. Get the chosen fragment's contract from compose.py --list-placeholders.

By content:

  • numeric chart: charts;
  • animation, number counter: motion and numbers;
  • video, screen recording, photo: video and images;
  • source code: code on a slide;
  • a URL shown on screen: QR code;
  • feedback on the deck or handing it to the organizer: edits and release.

Interface

Pick the template without asking. A new standalone page: blank with the shell. Embedding in another site, a fragment, or no header: bare, styles only.

Read the page layout, the visual language and the component index. The index maps the material's content to separate component references. Open only the ones you need.

If the material will be printed or saved as PDF, read print.

Another format or extending the system

Read the extension rules. Level theory, catalog internals and releases are not needed for a normal build.

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