agentleFS
ceedaragentsceedaragents/cyrus/skills/cyrus-setup-claude-auth/SKILL.md

cyrus-setup-claude-auth

Skill888 starsChanged 53 days agoApache-2.0View on GitHub

Configure Claude Code authentication for Cyrus — API key, OAuth token, or third-party provider.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check if credentials are already configured:

    line 14
  2. Distinctive:

    If the count is >= 1, inform the user:

    line 20
  3. Very specific:

    CRITICAL: Secrets must NEVER appear in the conversation: Do not explore ~/.claude/ looking for credential files.

    line 40
  4. Very specific:

    Check if claude is authenticated on this machine:

    line 50
  5. Very specific:

    If authenticated, instruct the user to run claude setup-token which will output a token.

    line 56
  6. Distinctive:

    After the user runs the command, verify the key was written:

    line 151
  7. Distinctive:

    If the count is 0, the credential was not saved.

    line 157

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CRITICAL: Never use Read, Edit, or Write tools on ~/.cyrus/.env or any file inside ~/.cyrus/. Use only Bash commands (grep, printf >>, etc.) to interact with env files — secrets must never be read into the conversation context.

Setup Claude Auth

Configures Claude Code credentials so Cyrus can run AI sessions.

Step 1: Check Existing Auth

Check if credentials are already configured:

grep -c -E '^(ANTHROPIC_API_KEY|CLAUDE_CODE_OAUTH_TOKEN)=' ~/.cyrus/.env 2>/dev/null || echo "0"

If the count is >= 1, inform the user:

Claude Code authentication is already configured. Skipping this step. To reconfigure, remove the existing key from ~/.cyrus/.env and re-run this skill.

Skip to completion.

Step 2: Choose Auth Method

Ask the user:

How would you like to authenticate Claude Code?

  1. Current account (easiest) — use the credentials from your active claude CLI session
  2. API Key — from console.anthropic.com
  3. Separate OAuth token — run claude setup-token to generate a token for a specific account
  4. Third-Party Provider — Vertex AI, AWS Bedrock, Azure, etc.

Step 3: Configure Credentials

CRITICAL: Secrets must NEVER appear in the conversation. Do not explore ~/.claude/ looking for credential files. Use only the methods below.

Detect the OS for the right clipboard command:

uname -s

Option 1: Current Account

Check if claude is authenticated on this machine:

claude auth status

If authenticated, instruct the user to run claude setup-token which will output a token.

To capture it safely, append a placeholder line to the env file, then open it in a GUI window so the user can paste the token:

grep -q '^CLAUDE_CODE_OAUTH_TOKEN=' ~/.cyrus/.env || echo 'CLAUDE_CODE_OAUTH_TOKEN=' >> ~/.cyrus/.env

Then open the file in a separate window — use whatever GUI editor is available:

# macOS: VS Code if available, otherwise TextEdit
code --new-window ~/.cyrus/.env 2>/dev/null || open -a TextEdit ~/.cyrus/.env

# Linux
code ~/.cyrus/.env 2>/dev/null || xdg-open ~/.cyrus/.env

Tell the user:

  1. Run claude setup-token in a separate terminal
  2. Copy the token it outputs
  3. I've opened ~/.cyrus/.env — find the CLAUDE_CODE_OAUTH_TOKEN= line
  4. Paste the token right after the = (no spaces, no newline)
  5. Save and close the file

Option 2: API Key

Instruct the user to copy their API key from the Anthropic Console, then provide the appropriate command:

macOS:

printf 'ANTHROPIC_API_KEY=%s\n' "$(pbpaste)" >> ~/.cyrus/.env

Linux:

printf 'ANTHROPIC_API_KEY=%s\n' "$(xclip -selection clipboard -o)" >> ~/.cyrus/.env

Universal fallback:

read -s -p "Paste your Anthropic API key: " val && printf 'ANTHROPIC_API_KEY=%s\n' "$val" >> ~/.cyrus/.env && echo " ✓ Saved"

Option 3: Separate OAuth Token

This is for when the user wants to generate a token for a different account than the one currently logged in (e.g., running claude setup-token on another machine).

Append the placeholder, then open the file for the user to paste:

grep -q '^CLAUDE_CODE_OAUTH_TOKEN=' ~/.cyrus/.env || echo 'CLAUDE_CODE_OAUTH_TOKEN=' >> ~/.cyrus/.env
# macOS
code --new-window ~/.cyrus/.env 2>/dev/null || open -a TextEdit ~/.cyrus/.env
# Linux
code ~/.cyrus/.env 2>/dev/null || xdg-open ~/.cyrus/.env

Tell the user:

  1. On the other machine, run claude setup-token
  2. Copy the token it outputs
  3. I've opened ~/.cyrus/.env — find CLAUDE_CODE_OAUTH_TOKEN= and paste the token after the =
  4. Save and close

Option 4: Third-Party Provider

Inform the user:

For third-party providers, you'll need to set provider-specific environment variables. See Third-Party Integrations for details.

Common configurations:

AWS Bedrock:

CLAUDE_CODE_USE_BEDROCK=1
AWS_REGION=us-east-1

Google Vertex AI:

CLAUDE_CODE_USE_VERTEX=1
CLOUD_ML_REGION=us-east5
ANTHROPIC_VERTEX_PROJECT_ID=your-project-id

Guide the user to add the appropriate variables to ~/.cyrus/.env using the clipboard-to-env pattern.

Step 4: Verify

After the user runs the command, verify the key was written:

grep -c -E '^(ANTHROPIC_API_KEY|CLAUDE_CODE_OAUTH_TOKEN|CLAUDE_CODE_USE_BEDROCK|CLAUDE_CODE_USE_VERTEX)=' ~/.cyrus/.env

If the count is 0, the credential was not saved. Ask the user to try again.

Completion

✓ Claude Code authentication configured.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.