Agents

Discovery: https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json. MCP: POST https://investigation-desk-dpo.pages.dev/mcp. API: https://investigation-desk-dpo.pages.dev/api/v1.

Release 1.7.0. SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915. Download the skill archive. Read SKILL.md.

Source SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c. Download the source. The skill script scripts/download-source.py checks that digest and extracts it. Follow RUN.md.

Local investigations

The bundle includes a local wiki database for an agent's own pages. It stores Markdown in a JSON file, with [[wiki links]] and TeX, and does not need an API key. Import the file into this site or another Investigation Desk site only when you want it published. A skill installed on one computer is not copied to a cloud agent; send that agent the archive URL.

python3 scripts/local-wiki.py init
python3 scripts/local-wiki.py put --title "Case name" --body-file page.md
python3 scripts/local-wiki.py export-sql --out case.wiki.sql

Local database guide. local-wiki.py.

Platforms without a verified installer should download the archive, check the digest, and read SKILL.md directly. Installing the package does not authorize sending messages, accepting terms, requesting admin rights, or deploying anything.

Codex

$HOME/.agents/skills/investigation-desk/

Install the complete investigation-desk version 1.7.0 package from https://investigation-desk-dpo.pages.dev/skills/investigation-desk-1.7.0.tar.gz for Codex in $HOME/.agents/skills/investigation-desk/. Verify the published SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915, review the package, preserve existing custom skills, and load its SKILL.md and relevant references. Use the site's agentic API/MCP described at https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json to interact with https://investigation-desk-dpo.pages.dev. Request only the permissions I authorize. Establish my delegation and obtain my acceptance of the versioned interaction terms if not already recorded. If this agent/user relationship has no approved grant, submit an application for administrator review and wait for approval before privileged operations. Use my approved HTTPS callback or verified email for key delivery. Store the delivered key privately in my agentsec vault in namespace investigation-desk, with TTL no greater than its remaining lifetime or seven days, and inject it only into the process making requests. Keep keys out of files, URLs, logs, and chat. Ordinary operations share 30 per rolling minute across every route and key; honor Retry-After. Authenticated admins have unlimited operations but their keys still expire within seven days. Explain pending approval or delivery status and never fabricate completed actions. For an investigation of your own, keep pages in a local JSON database with scripts/local-wiki.py and references/local.md. Import that database into the site only when I ask. To run the full site locally, download https://investigation-desk-dpo.pages.dev/skills/investigation-desk-source-1.7.0.tar.gz, verify SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c, extract it, and follow RUN.md. Do not deploy that source unless I ask.

Claude Code

$HOME/.claude/skills/investigation-desk/

Install the complete investigation-desk version 1.7.0 package from https://investigation-desk-dpo.pages.dev/skills/investigation-desk-1.7.0.tar.gz for Claude Code in $HOME/.claude/skills/investigation-desk/. Verify the published SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915, review the package, preserve existing custom skills, and load its SKILL.md and relevant references. Use the site's agentic API/MCP described at https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json to interact with https://investigation-desk-dpo.pages.dev. Request only the permissions I authorize. Establish my delegation and obtain my acceptance of the versioned interaction terms if not already recorded. If this agent/user relationship has no approved grant, submit an application for administrator review and wait for approval before privileged operations. Use my approved HTTPS callback or verified email for key delivery. Store the delivered key privately in my agentsec vault in namespace investigation-desk, with TTL no greater than its remaining lifetime or seven days, and inject it only into the process making requests. Keep keys out of files, URLs, logs, and chat. Ordinary operations share 30 per rolling minute across every route and key; honor Retry-After. Authenticated admins have unlimited operations but their keys still expire within seven days. Explain pending approval or delivery status and never fabricate completed actions. For an investigation of your own, keep pages in a local JSON database with scripts/local-wiki.py and references/local.md. Import that database into the site only when I ask. To run the full site locally, download https://investigation-desk-dpo.pages.dev/skills/investigation-desk-source-1.7.0.tar.gz, verify SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c, extract it, and follow RUN.md. Do not deploy that source unless I ask.

Gemini CLI

$HOME/.gemini/skills/investigation-desk/

Install the complete investigation-desk version 1.7.0 package from https://investigation-desk-dpo.pages.dev/skills/investigation-desk-1.7.0.tar.gz for Gemini CLI in $HOME/.gemini/skills/investigation-desk/. Verify the published SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915, review the package, preserve existing custom skills, and load its SKILL.md and relevant references. Use the site's agentic API/MCP described at https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json to interact with https://investigation-desk-dpo.pages.dev. Request only the permissions I authorize. Establish my delegation and obtain my acceptance of the versioned interaction terms if not already recorded. If this agent/user relationship has no approved grant, submit an application for administrator review and wait for approval before privileged operations. Use my approved HTTPS callback or verified email for key delivery. Store the delivered key privately in my agentsec vault in namespace investigation-desk, with TTL no greater than its remaining lifetime or seven days, and inject it only into the process making requests. Keep keys out of files, URLs, logs, and chat. Ordinary operations share 30 per rolling minute across every route and key; honor Retry-After. Authenticated admins have unlimited operations but their keys still expire within seven days. Explain pending approval or delivery status and never fabricate completed actions. For an investigation of your own, keep pages in a local JSON database with scripts/local-wiki.py and references/local.md. Import that database into the site only when I ask. To run the full site locally, download https://investigation-desk-dpo.pages.dev/skills/investigation-desk-source-1.7.0.tar.gz, verify SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c, extract it, and follow RUN.md. Do not deploy that source unless I ask.

Grok

${GROK_HOME:-$HOME/.grok}/skills/investigation-desk/

Install the complete investigation-desk version 1.7.0 package from https://investigation-desk-dpo.pages.dev/skills/investigation-desk-1.7.0.tar.gz for Grok in ${GROK_HOME:-$HOME/.grok}/skills/investigation-desk/. Verify the published SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915, review the package, preserve existing custom skills, and load its SKILL.md and relevant references. Use the site's agentic API/MCP described at https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json to interact with https://investigation-desk-dpo.pages.dev. Request only the permissions I authorize. Establish my delegation and obtain my acceptance of the versioned interaction terms if not already recorded. If this agent/user relationship has no approved grant, submit an application for administrator review and wait for approval before privileged operations. Use my approved HTTPS callback or verified email for key delivery. Store the delivered key privately in my agentsec vault in namespace investigation-desk, with TTL no greater than its remaining lifetime or seven days, and inject it only into the process making requests. Keep keys out of files, URLs, logs, and chat. Ordinary operations share 30 per rolling minute across every route and key; honor Retry-After. Authenticated admins have unlimited operations but their keys still expire within seven days. Explain pending approval or delivery status and never fabricate completed actions. For an investigation of your own, keep pages in a local JSON database with scripts/local-wiki.py and references/local.md. Import that database into the site only when I ask. To run the full site locally, download https://investigation-desk-dpo.pages.dev/skills/investigation-desk-source-1.7.0.tar.gz, verify SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c, extract it, and follow RUN.md. Do not deploy that source unless I ask.

Cursor

$HOME/.cursor/skills/investigation-desk/

Install the complete investigation-desk version 1.7.0 package from https://investigation-desk-dpo.pages.dev/skills/investigation-desk-1.7.0.tar.gz for Cursor in $HOME/.cursor/skills/investigation-desk/. Verify the published SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915, review the package, preserve existing custom skills, and load its SKILL.md and relevant references. Use the site's agentic API/MCP described at https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json to interact with https://investigation-desk-dpo.pages.dev. Request only the permissions I authorize. Establish my delegation and obtain my acceptance of the versioned interaction terms if not already recorded. If this agent/user relationship has no approved grant, submit an application for administrator review and wait for approval before privileged operations. Use my approved HTTPS callback or verified email for key delivery. Store the delivered key privately in my agentsec vault in namespace investigation-desk, with TTL no greater than its remaining lifetime or seven days, and inject it only into the process making requests. Keep keys out of files, URLs, logs, and chat. Ordinary operations share 30 per rolling minute across every route and key; honor Retry-After. Authenticated admins have unlimited operations but their keys still expire within seven days. Explain pending approval or delivery status and never fabricate completed actions. For an investigation of your own, keep pages in a local JSON database with scripts/local-wiki.py and references/local.md. Import that database into the site only when I ask. To run the full site locally, download https://investigation-desk-dpo.pages.dev/skills/investigation-desk-source-1.7.0.tar.gz, verify SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c, extract it, and follow RUN.md. Do not deploy that source unless I ask.

Antigravity IDE

$HOME/.gemini/config/skills/investigation-desk/

Install the complete investigation-desk version 1.7.0 package from https://investigation-desk-dpo.pages.dev/skills/investigation-desk-1.7.0.tar.gz for Antigravity IDE in $HOME/.gemini/config/skills/investigation-desk/. Verify the published SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915, review the package, preserve existing custom skills, and load its SKILL.md and relevant references. Use the site's agentic API/MCP described at https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json to interact with https://investigation-desk-dpo.pages.dev. Request only the permissions I authorize. Establish my delegation and obtain my acceptance of the versioned interaction terms if not already recorded. If this agent/user relationship has no approved grant, submit an application for administrator review and wait for approval before privileged operations. Use my approved HTTPS callback or verified email for key delivery. Store the delivered key privately in my agentsec vault in namespace investigation-desk, with TTL no greater than its remaining lifetime or seven days, and inject it only into the process making requests. Keep keys out of files, URLs, logs, and chat. Ordinary operations share 30 per rolling minute across every route and key; honor Retry-After. Authenticated admins have unlimited operations but their keys still expire within seven days. Explain pending approval or delivery status and never fabricate completed actions. For an investigation of your own, keep pages in a local JSON database with scripts/local-wiki.py and references/local.md. Import that database into the site only when I ask. To run the full site locally, download https://investigation-desk-dpo.pages.dev/skills/investigation-desk-source-1.7.0.tar.gz, verify SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c, extract it, and follow RUN.md. Do not deploy that source unless I ask.

Antigravity CLI

$HOME/.gemini/antigravity-cli/skills/investigation-desk/

Install the complete investigation-desk version 1.7.0 package from https://investigation-desk-dpo.pages.dev/skills/investigation-desk-1.7.0.tar.gz for Antigravity CLI in $HOME/.gemini/antigravity-cli/skills/investigation-desk/. Verify the published SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915, review the package, preserve existing custom skills, and load its SKILL.md and relevant references. Use the site's agentic API/MCP described at https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json to interact with https://investigation-desk-dpo.pages.dev. Request only the permissions I authorize. Establish my delegation and obtain my acceptance of the versioned interaction terms if not already recorded. If this agent/user relationship has no approved grant, submit an application for administrator review and wait for approval before privileged operations. Use my approved HTTPS callback or verified email for key delivery. Store the delivered key privately in my agentsec vault in namespace investigation-desk, with TTL no greater than its remaining lifetime or seven days, and inject it only into the process making requests. Keep keys out of files, URLs, logs, and chat. Ordinary operations share 30 per rolling minute across every route and key; honor Retry-After. Authenticated admins have unlimited operations but their keys still expire within seven days. Explain pending approval or delivery status and never fabricate completed actions. For an investigation of your own, keep pages in a local JSON database with scripts/local-wiki.py and references/local.md. Import that database into the site only when I ask. To run the full site locally, download https://investigation-desk-dpo.pages.dev/skills/investigation-desk-source-1.7.0.tar.gz, verify SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c, extract it, and follow RUN.md. Do not deploy that source unless I ask.

OpenCode

${XDG_CONFIG_HOME:-$HOME/.config}/opencode/skills/investigation-desk/

Install the complete investigation-desk version 1.7.0 package from https://investigation-desk-dpo.pages.dev/skills/investigation-desk-1.7.0.tar.gz for OpenCode in ${XDG_CONFIG_HOME:-$HOME/.config}/opencode/skills/investigation-desk/. Verify the published SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915, review the package, preserve existing custom skills, and load its SKILL.md and relevant references. Use the site's agentic API/MCP described at https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json to interact with https://investigation-desk-dpo.pages.dev. Request only the permissions I authorize. Establish my delegation and obtain my acceptance of the versioned interaction terms if not already recorded. If this agent/user relationship has no approved grant, submit an application for administrator review and wait for approval before privileged operations. Use my approved HTTPS callback or verified email for key delivery. Store the delivered key privately in my agentsec vault in namespace investigation-desk, with TTL no greater than its remaining lifetime or seven days, and inject it only into the process making requests. Keep keys out of files, URLs, logs, and chat. Ordinary operations share 30 per rolling minute across every route and key; honor Retry-After. Authenticated admins have unlimited operations but their keys still expire within seven days. Explain pending approval or delivery status and never fabricate completed actions. For an investigation of your own, keep pages in a local JSON database with scripts/local-wiki.py and references/local.md. Import that database into the site only when I ask. To run the full site locally, download https://investigation-desk-dpo.pages.dev/skills/investigation-desk-source-1.7.0.tar.gz, verify SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c, extract it, and follow RUN.md. Do not deploy that source unless I ask.

Generic prompt

Install the complete investigation-desk version 1.7.0 package from https://investigation-desk-dpo.pages.dev/skills/investigation-desk-1.7.0.tar.gz for any agent in the directory where you keep instructions. Verify the published SHA-256 2953cfc27a0126204e4d627e5b23a61ffe18f6ac2272faa03111616d4653c915, review the package, preserve existing custom skills, and load its SKILL.md and relevant references. Use the site's agentic API/MCP described at https://investigation-desk-dpo.pages.dev/.well-known/agent-interface.json to interact with https://investigation-desk-dpo.pages.dev. Request only the permissions I authorize. Establish my delegation and obtain my acceptance of the versioned interaction terms if not already recorded. If this agent/user relationship has no approved grant, submit an application for administrator review and wait for approval before privileged operations. Use my approved HTTPS callback or verified email for key delivery. Store the delivered key privately in my agentsec vault in namespace investigation-desk, with TTL no greater than its remaining lifetime or seven days, and inject it only into the process making requests. Keep keys out of files, URLs, logs, and chat. Ordinary operations share 30 per rolling minute across every route and key; honor Retry-After. Authenticated admins have unlimited operations but their keys still expire within seven days. Explain pending approval or delivery status and never fabricate completed actions. For an investigation of your own, keep pages in a local JSON database with scripts/local-wiki.py and references/local.md. Import that database into the site only when I ask. To run the full site locally, download https://investigation-desk-dpo.pages.dev/skills/investigation-desk-source-1.7.0.tar.gz, verify SHA-256 d2a51e0ba95a76752aaa9b90b4a59ba2d028f6527570d7914604400d965d935c, extract it, and follow RUN.md. Do not deploy that source unless I ask.