agenticnotetaking/skills/mono
skills/mono/SKILL.md
--- tldr: Register a working subdirectory focus in a monorepo category: utility --- # /eidos:mono Register which subdirectory you're actually working in when Claude Code opens at the repo root. Stored per-user outside the repo, injected automatically at session start. ## Usage ``` /eidos:mono set <path> # set focus to subdirectory /eidos:mono clear # remove focus for this repo /eidos:mono list # show all mappings /eidos:mono # show current mapping or usage `
$ install --global
skillsauthnpx skillsauth add agenticnotetaking/eidos skills/monoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 6:28 AM56.6s2 files scanned
SKILL.md
- tldr:
- Register a working subdirectory focus in a monorepo
- category:
- utility
/eidos:mono
Register which subdirectory you're actually working in when Claude Code opens at the repo root. Stored per-user outside the repo, injected automatically at session start.
Usage
/eidos:mono set <path> # set focus to subdirectory
/eidos:mono clear # remove focus for this repo
/eidos:mono list # show all mappings
/eidos:mono # show current mapping or usage
Instructions
1. Determine Repo Root
Run git rev-parse --show-toplevel to get the repo root.
If not in a git repo, use the current working directory.
2. Route by Command
Parse the arguments to determine which command to run.
set <path>
- Resolve
<path>relative to the repo root - Check if the path exists as a directory:
- Exists: proceed
- Doesn't exist: check for close matches (partial name, typo). If a likely match is found, suggest it. Otherwise ask the user for clarification.
- Run:
bash "$PLUGIN_ROOT/scripts/mono_write.sh" set "<repo_root>" "<path>" - Confirm:
Mono focus set: **<path>** in \<repo_root>``
clear
- Run:
bash "$PLUGIN_ROOT/scripts/mono_write.sh" clear "<repo_root>" - Confirm:
Mono focus cleared for \<repo_root>``
list
- Read
~/.config/eidos/mono.yaml - If file doesn't exist or is empty:
No mono mappings set. - Otherwise, list all mappings. Highlight the current repo's entry (if any):
Mono mappings (~/.config/eidos/mono.yaml):
→ /Users/omni/repos/mono: repo/eidos ← current repo
/Users/omni/repos/other: packages/core
No args
- Run:
bash "$PLUGIN_ROOT/scripts/mono_read.sh" "<repo_root>" - If mapping exists:
Mono focus: **<subpath>** (\<repo_root>/<subpath>`)` - If no mapping: show usage summary
3. Access
The PLUGIN_ROOT variable points to the eidos plugin directory.
Scripts are at $PLUGIN_ROOT/scripts/mono_read.sh and $PLUGIN_ROOT/scripts/mono_write.sh.
PLUGIN_ROOT is available as CLAUDE_PLUGIN_ROOT environment variable, or can be derived from the skill's own path.
Output
- Reads/writes:
~/.config/eidos/mono.yaml(external, user-specific) - No repo files modified
Related Skills
agenticnotetaking/skills/outbox
development
VerifiedTrustedCommunity
--- tldr: Check the status of messages you sent to peer inboxes category: core --- # /eidos:outbox Find messages **you sent** to peer repos and report their status. Your sent messages live in the peers' inboxes, not here. So this skill sweeps every registered peer and reads back what became of them. This is the mirror of [[spec - inbox skill - read and act on your own inbox]]. - The inbox is messages others sent **to** you. You own and edit it. - The outbox is messages you sent **to** others.
53SKILL.mdUpdated Jun 9, 2026
agenticnotetaking/skills/message
development
VerifiedTrustedCommunity
--- tldr: Send a message to a peer repo's inbox category: core --- # /eidos:message Write a message into another repo's `agent-inbox/`. The recipient is a peer repo, addressed by its registered name. See [[spec - agent communication - cross repo inboxes with append only messages and registry resolution]]. ## Usage ``` /eidos:message [recipient repo] [what to say] ``` ## Instructions ### 1. Resolve the recipient - Identify the recipient repo name. Ask if not given. - Resolve its path: `
53SKILL.mdUpdated Jun 9, 2026
agenticnotetaking/skills/inbox
development
VerifiedTrustedCommunity
--- tldr: Read and act on your own inbox category: core --- # /eidos:inbox List and work through messages other repos have left in your `agent-inbox/`. You own this inbox. You may edit its files freely. Agents from other repos may push **new** messages into your inbox at any time. They never edit existing files. Only you do. So re-check the inbox. Don't assume it is unchanged since you last looked. See [[c - foreign agents append to an inbox - only the owner edits in place]]. See [[spec - ag
53SKILL.mdUpdated Jun 9, 2026
agenticnotetaking/skills/archive
tools
VerifiedTrustedCommunity
--- tldr: Move done files into archive subdirs (memory/ and agent-inbox/) category: utility --- # /eidos:archive Retire finished files into the `archive/` sibling of their directory. Done `memory/` files into `memory/archive/`, done inbox messages into `agent-inbox/archive/`. A `git mv`, never a rename. The basename is preserved, so wiki links keep resolving. See [[c - archiving moves done files into an archive subdir preserving basename and links]]. ## Usage ``` /eidos:archive [optional fil
53SKILL.mdUpdated Jun 9, 2026