Run any Skill in Manus with one click

arclink-resources

Stars3

Forks0

UpdatedMay 8, 2026 at 06:34

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sirouk

sirouk/arclink

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

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.

ArcLink Resources

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

Contract

read only the current user's local ArcLink state under $HERMES_HOME/state
never print passwords, tokens, deploy keys, bootstrap tokens, or raw secret files
use the current user's home alias as the vault home base: ~/ArcLink
in VS Code and shell-facing explanations, prefer /home/<user>/ArcLink over central service-user paths such as /home/arclink/...
explain that the shared Vault and control rails are already wired into the agent by default

Expected Response Shape

When answering the user, include the useful links and omit credentials:

Web access: Hermes dashboard, dashboard username, code workspace, workspace root, and ArcLink vault path
Host helper: ~/.local/bin/arclink-agent-hermes
Backups: ~/.local/bin/arclink-agent-configure-backup and the warning not to reuse shared deploy keys
Shared ArcLink links: shared Notion SSOT, Notion webhook note, and the local ~/ArcLink vault path
Optional remote agent CLI: the curl installer command, /ssh-key <public key> callback, generated wrapper name, and SSH target when the local state has a tailnet host and Unix user

Guardrails

do not ask the user to paste or reveal their shared password
do not claim the password is unknown in a way that encourages recovery in chat; say credentials are intentionally omitted and access reset goes through Curator/operator
do not inspect other users' home directories
do not read central deployment secrets such as arclink.env, .arclink-operator.env, or backup key material from a user-agent session
if a path points at the shared vault, translate it to the user-visible ~/ArcLink alias whenever possible

More from this repository

same repository

arclink-first-contact

sirouk/arclink

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.

2026-06-173

arclink-notion-knowledge

sirouk/arclink

Use for shared ArcLink Notion knowledge retrieval through the default shared notion.search / notion.fetch / notion.query rail.

2026-06-173

arclink-vaults

sirouk/arclink

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.

2026-06-173

arclink-academy

sirouk/arclink

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.

2026-06-093

arclink-upgrade-orchestrator

sirouk/arclink

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.

2026-06-013

arclink-ssot

sirouk/arclink

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.

2026-05-043

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.

ArcLink Resources

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

Contract

read only the current user's local ArcLink state under $HERMES_HOME/state
never print passwords, tokens, deploy keys, bootstrap tokens, or raw secret files
use the current user's home alias as the vault home base: ~/ArcLink
in VS Code and shell-facing explanations, prefer /home/<user>/ArcLink over central service-user paths such as /home/arclink/...
explain that the shared Vault and control rails are already wired into the agent by default

Expected Response Shape

When answering the user, include the useful links and omit credentials:

Web access: Hermes dashboard, dashboard username, code workspace, workspace root, and ArcLink vault path
Host helper: ~/.local/bin/arclink-agent-hermes
Backups: ~/.local/bin/arclink-agent-configure-backup and the warning not to reuse shared deploy keys
Shared ArcLink links: shared Notion SSOT, Notion webhook note, and the local ~/ArcLink vault path
Optional remote agent CLI: the curl installer command, /ssh-key <public key> callback, generated wrapper name, and SSH target when the local state has a tailnet host and Unix user

Guardrails

do not ask the user to paste or reveal their shared password
do not claim the password is unknown in a way that encourages recovery in chat; say credentials are intentionally omitted and access reset goes through Curator/operator
do not inspect other users' home directories
do not read central deployment secrets such as arclink.env, .arclink-operator.env, or backup key material from a user-agent session
if a path points at the shared vault, translate it to the user-visible ~/ArcLink alias whenever possible