メニュー
Use when an enrolled user asks for /arclink-resources, ArcLink links, dashboard/code workspace URLs, the remote helper, backup setup, SSH setup, or where the shared vault lives from their own agent lane.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use after ArcLink enrolls a user agent and installs the default skills/MCP config to verify live ArcLink MCP and qmd calls, resolve default vault subscriptions, materialize plugin-managed context state, and complete first-contact orientation.
Use for shared ArcLink Notion knowledge retrieval through the default shared notion.search / notion.fetch / notion.query rail.
Use to inspect the active ArcLink vault catalog, curate subscribed vs default vaults, inspect the canonical managed-memory payload that feeds plugin context, and trigger subscription refresh without changing qmd retrieval access.
Use when Academy Mode is active, when the Captain asks an Agent to become a subject-matter specialist, or when the Agent needs to gather, compress, propose, and maintain Academy training resources for weekly continuing education.
Use when Operator Raven, Curator, or the operator needs to check whether the deployed ArcLink host is behind its tracked upstream, summarize the upgrade state, or queue/run the guarded upgrade path.
Use to connect an enrolled user agent to a shared Notion SSOT workspace with read, insert, page/database creation, and update rails while refusing archive/delete by default.
| name | arclink-resources |
| description | Use when an enrolled user asks for /arclink-resources, ArcLink links, dashboard/code workspace URLs, the remote helper, backup setup, SSH setup, or where the shared vault lives from their own agent lane. |
Use this skill when the user asks for their ArcLink resources, links, workspace, dashboard, remote helper, backup setup, or shared vault location.
The arclink-managed-context plugin can answer /arclink-resources directly from local state. If you need a human-readable fallback, run:
scripts/show-resources.sh
$HERMES_HOME/state~/ArcLink/home/<user>/ArcLink over central service-user paths such as /home/arclink/...When answering the user, include the useful links and omit credentials:
~/.local/bin/arclink-agent-hermes~/.local/bin/arclink-agent-configure-backup and the warning not to reuse shared deploy keys~/ArcLink vault path/ssh-key <public key> callback, generated wrapper name, and SSH target when the local state has a tailnet host and Unix userarclink.env, .arclink-operator.env, or backup key material from a user-agent session~/ArcLink alias whenever possible