agentleFS
jurgendnjurgendn/agent-skills/skills/init-workspace/SKILL.md

init-workspace

Skill10 starsChanged 57 days agoNo licenceView on GitHub

Initialize a structured Obsidian-style workspace for learning, research notebooks, papers, academic applications, talks, test preparation, theory, and similar note-centric knowledge work. Use when the user asks to set up, start, initialize, scaffold, or bootstrap a vault/workspace for work organized primarily through notes and written artifacts. Do not use for software repositories, software applications, experiment codebases, or other coding projects. Ask one short intake batch covering the work and its definition of done, project title plus confirmed target directory, and any differences from the typical case. Then use a ready template as-is, adapt the closest template while keeping its contract internally consistent, or synthesize a lean bespoke vault when none fits. Write only into the confirmed target vault; never modify this skill''s templates during a run. This skill creates structure and routing, not the downstream content itself.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.