Saucebox Registry
← Browse

@block/api-setup

A

Set up API integration with configuration and helper scripts

skillclaude

Install

agr install @block/api-setup --target claude

Writes 2 files into .claude/skills/, pinned to git-1766b70c.

  • .claude/skills/api-setup/SKILL.md
  • .claude/skills/api-setup/setup.sh

Document

name: api-setup description: Set up API integration with configuration and helper scripts author: goose version: "1.0" tags:

  • api
  • integration
  • setup

API Setup

This skill helps you set up a new API integration with our standard configuration.

Steps

  1. Run setup.sh <api-name> to create the integration directory
  2. Copy templates/config.template.json to your integration directory
  3. Update the config with your API credentials
  4. Test the connection

Configuration

The config template includes:

  • api_key: Your API key (get from the provider's dashboard)
  • endpoint: API endpoint URL
  • timeout: Request timeout in seconds (default: 30)

Verification

After setup, verify:

  • Config file is valid JSON
  • API key is set and not a placeholder
  • Test connection succeeds

Troubleshooting

Connection Timeout

If you experience connection timeouts:

  1. Check your network connection
  2. Verify the endpoint URL is correct
  3. Increase the timeout value in config

Authentication Errors

If you get 401/403 errors:

  1. Verify your API key is correct
  2. Check if the key has the required permissions
  3. Ensure the key hasn't expired

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-1766b70c735c2026-07-31