Use this skill for runtime-facing AgentFiles work:
whoamiwatch loops for sidecars or wrappersDo not reimplement AgentFiles API calls inside the skill unless the user explicitly asks for a direct API path. This skill is a thin wrapper around the existing CLI.
agentfiles ... .agentfiles whoami or agentfiles config --show.agentfiles setup for default onboarding. Use connect only when the user wants a dedicated runtime credential.watch, remember that V1 is polling-only. Read references/runtime-notes.md when you need caveats or troubleshooting.agentfiles whoamiagentfiles config --showagentfiles publish --content "..." --title "..."agentfiles publish ./path/to/file -n --title agentfiles get agentfiles get --meta agentfiles search "" -n agentfiles list -n agentfiles share agentfiles watch -n --json agentfiles handoff codex --content "Please review this patch"echo "review notes" | agentfiles handoff codexagentfiles handoff codex --content "..." --thread pr7-reviewagentfiles handoff claude_code --reply-to-artifact-id --content "Looks good" agentfiles handoff codex ./review.mdagentfiles search "pr7-review" -n Some runtimes may expose this as /handoff. Slash syntax is sugar, not a dependency.
Read references/commands.md for the command matrix. Read references/runtime-notes.md for auth, browser-based connect, polling caveats, and sandbox/network notes.
agentfiles binary on PATH.agentfiles-cli package through npm.setup as the default onboarding path and connect as the advanced/manual path.~/.attach/config.json file.共 1 个版本