Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
HTML agent-skillsai-agentsarchitecture-diagramclaude-codeclaude-skillscodexcoding-agentsdeepseek-harnessdeveloper-toolsdiagramsdiagrams-as-codedsh-pluginflowchartllmmermaidopencodesequence-diagramsoftware-architecturesystem-designvisualization
docs(agents): discover the selected installation source
tt-a1i62bd6d265c28
diff --git a/AGENTS.md b/AGENTS.mdindex 3291bd8b..c24d318d 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -7,7 +7,7 @@ Follow [CONTRIBUTING.md](CONTRIBUTING.md) for repository changes and [REVIEWING.Install, update, reinstall, or remove a live Archify installation only when the user explicitly requests that action. Repository editing, testing, reviewing, publishing, or syncing does not authorize installation. This applies to Skills CLI, manual ZIP copies, and DSH plugins. Reuse authorization already given for the same action and scope; ask only for unresolved decisions.- Keep the source, Skill/package, target agents, and global/project scope within the request. Avoid bulk operations or force flags that expand that scope. An update notification is informational.-- Before a Skills CLI install, run `npx -y skills add tt-a1i/archify --list --full-depth` and verify exactly one Skill named `archify`. Stop on failed or ambiguous discovery.+- Before a Skills CLI install, discover the selected source with `npx -y skills add <source> --list --full-depth` (default source: `tt-a1i/archify`) and verify exactly one Skill named `archify`. For an explicitly requested durable local source, inspect that checkout. Stop on failed or ambiguous discovery.- Use the canonical remote source by default. Use a local source only when requested, from a durable checkout; live symlinks must not point into temporary directories or disposable worktrees.- Preserve unrelated files and existing unmanaged destinations. Report a destination conflict before replacing it unless that exact replacement is already explicitly authorized; use the installer's documented conflict handling within the approved scope.- Report the action, source, targets, and result, including skipped or failed destinations. A partial installation is not a complete success.