write agent
- Repo stars 0
- Author repo skills-registry
- Domain
- Documentation
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Auto Documentation
Auto updates Documentation and Context
## README File
1. **Directory Structure**: Update the README.md in the 'Directory Structure' section based on the up to date directory structure. The 'build' directory represents a separate cloned repositories outside of this one.
- Only required to include information relative to the repository directory structure
- Align all right hand comments to the same indent level for readability
- For Directories, only include important directories, it is not required to include all nested directories.
- Ensure to include the agent specific directories (.claude, .gemini, etc.) and top-level subdirectoriesfor discovery
- For Filenames, only include important filenames, it is not required to include all filenames.
- Ensure to include all agent specific files (AGENTS.md, CLAUDE.md, GEMINI.md, etc.) for discovery
2. **Quick Links**: Update Quick Links based on the Markdown Headers as appropriate
3. **Docs Folder**: Update files in the @./docs folder after major milestones and major additions to the project
4. **Links**: Ensure that all links in the README.md are up to date and not broken.
- This includes links to files, directories, and external links.
## Startup Context Files
All Context files (@CLAUDE.md, @GEMINI.md, etc.) should update the @AGENTS.md file, instead of their individual files. Based off the @README.md file at minimal. These context files should not be overly verbose, while still providing contextual information.
---
> Source: [akamlani/agent-skills](https://github.com/akamlani/agent-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
Sections and files
Listed in source order.
sections -> README File → Startup Context Files
terms -> Directory Structure · Quick Links · Docs Folder · Links
files/cmd -> README.md · AGENTS.md · CLAUDE.md · GEMINI.md · ./docs · akamlani/agent-skills · github.com/akamlani/agent-skills
body sha256 -> 678023780800
README File
Directory Structure: Update the README.md in the 'Directory Structure' section based on the up to date directory structure. The 'build' directory represents a separate cloned repositories outside of this one. Only required to include information relative to the repository directory structure Align all right hand comments to the same indent level for readability For Directories, only include important directories, it is not required to include all nested directories.
Startup Context Files
All Context files (@CLAUDE.md, @GEMINI.md, etc.) should update the @AGENTS.md file, instead of their individual files. Based off the @README.md file at minimal. These context files should not be overly verbose, while still providing contextual information. Source: akamlani/agent-skills — distributed by TomeVault.