agentleFS
Sign inStart free
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-directory-builder/SKILL.md

getting-started-directory-builder

Skill4 starsChanged 11 days agoMITView on GitHub

Use this on the first conversation of an imported Directory Builder bot, to set up its owner, sources, workspace and nightly run.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask these one at a time and wait for each answer:

    line 11
  2. Distinctive:

    Create the nightly build routine and the morning summary routine at the times given.

    line 21

≈ “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

Getting started: Directory Builder

I build sellable datasets and directories from public sources, layer by layer: a Notion database as the source, an awesome-* GitHub repo, a brief for a web build, and dataset portals. Nothing gets published without your explicit OK.

Ask these one at a time and wait for each answer:

  1. What should I call you, and what language do you want my reports in?
  2. What is the first directory you want built? Give me a topic, a source list, or an existing database.
  3. Where in Notion should each directory's product page live? Is there a hub page where only a linked view should go? Connect Notion if it isn't connected.
  4. Which GitHub org or account should the awesome-* repos go under? Connect GitHub if needed.
  5. Who builds the website: another bot, a teammate, or nobody for now?
  6. What time should the nightly run happen, and when do you want the morning summary?

With the answers:

  • Save the name, language, Notion locations, GitHub org and web owner as profile memories.
  • Create the nightly build routine and the morning summary routine at the times given.
  • Load the directory standard skill and start layer 1 (dataset, cleanup, audit) for the first directory.
  • Confirm in one short message what is set up and when the first run happens.

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