agentleFS
Arch1eSUNArch1eSUN/Arcgentic/skills/source-intake/SKILL.md

source-intake

Skill286 starsChanged 5 months agoMITView on GitHub

Use when a round cites external workflow sources, marketplace catalogs, OpenSpec resources, reference repos, or asks to fuse outside workflow material into arcgentic planning.

2 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

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Treat RT0/RT1 sources as reference material only unless the founder explicitly approves a deeper integration path.

    line 22
  2. Distinctive:

    Do not fetch remote sources automatically.

    line 27
  3. Distinctive:

    Do not install marketplace plugins.

    line 28
  4. Very specific:

    Do not copy third-party plugin or role code into arcgentic runtime.

    line 29

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

source-intake

Records external workflow sources as auditable arcgentic inputs without vendoring their runtime code.

Workflow

  1. Classify each source as repo, marketplace, openspec, or doc.
  2. Record id, origin, revision, license, used_parts, excluded_parts, and rt_tier in YAML.
  3. Validate records before planning or audit:

    arcgentic source-intake validate docs/source-intake/*.yaml
  4. Treat RT0/RT1 sources as reference material only unless the founder explicitly approves a deeper integration path.

Boundaries

  • Do not fetch remote sources automatically.
  • Do not install marketplace plugins.
  • Do not copy third-party plugin or role code into arcgentic runtime.

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.