new-entry
Skill38 starsChanged 9 months agoMITView on GitHub
Create a new registry entry with guided wizard. Supports components, data-objects, functions, services, and other ArchiMate element types.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- crawl-apisSkill
- crawl-dataSkill
- dashboardSkill
- deploySkill
- enterprise-platform-archiSkill
- scaffold-componentSkill
- validateSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
If arguments not provided, ask the user:
- Distinctive: line 25
Do NOT hardcode paths: Always discover dynamically:
- Very specific: line 29
Use the folder: field for that type to determine the target directory
- Very specific: line 37
Read _template.md in the target folder for structure
- Distinctive: line 38
Read 1-2 existing entries in target folder for pattern reference
- Distinctive: line 39
Create filename: kebab-case of name (e.g., "Payment Record" -> "payment-record.md")
- Distinctive: line 45
Write file to correct folder
- Distinctive: line 83
Always use kebab-case for filenames
- Distinctive: line 85
Run validation after creation to catch issues early
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Create New Registry Entry
Guide the user through creating a properly structured registry entry.
Arguments
$1- Element type: component, software-system, data-concept, data-aggregate, data-entity, domain-event, api-endpoint, etc.$2+- Element name (can have spaces)
If arguments not provided, ask the user:
- What type of element?
- What is the element name?
- Which domain does it belong to?
Element Type to Folder Mapping
Do NOT hardcode paths. Always discover dynamically:
- Read
models/registry-mapping.yaml - Find the element type under
elements: - Use the
folder:field for that type to determine the target directory - Prepend
registry-v2/to the folder path
This ensures the skill works even if users rename layers, types, or restructure folders.
Workflow
- Determine element type and target folder
- Read
_template.mdin the target folder for structure - Read 1-2 existing entries in target folder for pattern reference
- Create filename: kebab-case of name (e.g., "Payment Record" -> "payment-record.md")
- Fill frontmatter:
- name: [provided name]
- owner: TBD
- status: draft
- [type-specific fields and relationships from template]
- Write file to correct folder
- Run validation:
python scripts/validate.py
Response Format
**Created:** registry-v2/<layer>/<type-folder>/element-name.md
**Frontmatter:**
---
type: <element-type>
name: <Element Name>
owner: TBD
status: draft
<type-specific fields from template>
---
**Next Steps:**
1. Fill in TBD fields
2. Add description in the body
3. Run /validate to verify
Would you like me to help fill in any of the TBD fields?Domain-Specific Fields
For data elements (concepts, aggregates, entities), also include:
- Relationship to parent element (data concept -> aggregate -> entity chain)
- classification: internal/business-confidential/pii
For software elements (systems, subsystems), also include:
- sourcing: in-house/vendor/hybrid
- vendor: (if vendor)
- realizes_component: Which component this system supports
Notes
- Always use kebab-case for filenames
- Mark unknown fields as TBD rather than guessing
- Run validation after creation to catch issues early
- Suggest wiring relationships as a follow-up action
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
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.

