agentleFS
DINAKAR-SDINAKAR-S/company-ai-os/.claude/skills/new-entity/SKILL.md

new-entity

Skill2 starsChanged 3 months agoMITView on GitHub

Scaffold a new entity note (department, project, tool, client, person) from the template, cross-link it, and index it. Use when the user says "add an entity", "new department/project/tool note", or "/new-entity <name>".

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. fpindej/netrock★ 234same name
    2. genfeedai/genfeed.ai★ 4same 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 repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the one-line "What it is" and whatever details the user provides.

    line 13
  2. Very specific:

    Add [[wikilinks]] both ways: link related entities in this note, and add a [[<Name>]] link in at least one existing note ([[Company]] or a …

    line 14
  3. Very specific:

    Add the entry to index.md under the right category.

    line 16
  4. Very specific:

    If it has a path:, add a row to entities/Routing.md.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

New Entity

Given a name (and optionally a type + real folder path):

  1. Copy _templates/entity.md to entities/<Name>.md (filename = common name, spaces OK).
  2. Fill frontmatter: type, path (forward slashes; ask if unknown — never guess), aliases (every other name it goes by), tags, status: active, updated: <today>.
  3. Write the one-line "What it is" and whatever details the user provides.
  4. Add [[wikilinks]] both ways: link related entities in this note, and add a [[<Name>]] link in at least one existing note ([[Company]] or a department).
  5. Add the entry to index.md under the right category.
  6. If it has a path:, add a row to entities/Routing.md.
  7. Log: ## [date] ingest | new entity <Name> → entities/<Name>.md

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.