SERP TOC

Use this skill as the start-here routing layer for SERP work. The serp repo is the org-level docs hub, not the source of truth for most code, secrets, or runtime operations.

Workflow

1. Start in the SERP docs hub before guessing.

• Read README.md and docs/README.md in serp.
• For repo lookup, prefer docs/REPOS.local.md when it exists. Fall back to docs/REPOS.md for the shared inventory.
• Use docs/WORKFLOWS.md when the real question is where something should live.

2. Route to the owning repo quickly.

• For server, infrastructure, operator access, SSH, Jupyter, or runtime ops, jump to docs/knowledge/server-systems.md in serp first, then follow its pointers into serp-server.
• For secrets, env values, tokens, or secret storage, jump to the secrets.serp.co entry in docs/REPOS.local.md, then inspect /Users/devin/dev/repos/secrets.serp.co/README.md.
• For general app, auth, DB, monorepo, or utility code, find the repo in docs/REPOS.local.md and read that repo's README.md before doing anything app-specific.