Configure an Exa client without leaking credentials or mixing API-key, MCP OAuth, enterprise managed authorization, and payment-protocol trust models.

MITAuto-check passedBackend & APIs

Install Exa Install Auth

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill exa-install-auth -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace exa-install-auth --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/exa-install-auth .claude/skills/exa-install-auth && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
exa-install-auth
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
585 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Configure an Exa client without leaking credentials or mixing API-key, MCP OAuth, enterprise managed authorization, and payment-protocol trust models.

  • Works in 6 steps: Inventory the runtime, endpoint family,… → Choose exactly one supported… → Place the credential in the approved… → …
  • Reviewing this Exa boundary
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
  • Needs EXA_API_KEY

What it does

Exa Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure an Exa client without leaking credentials or mixing API-key, MCP OAuth, enterprise managed authorization, and payment-protocol trust models. Use when operating or reviewing this Exa boundary. Trigger with "Exa install auth", "review Exa install auth", or "fix Exa install auth".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live Exa work requires network access

It sits in Backend & APIs, covering OAuth and OpenID Connect and Authorization and RBAC. It works with Model Context Protocol and Exa. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Reviewing this Exa boundary
  • With Exa install auth
  • Review Exa install auth
  • Fix Exa install auth

Example prompts

  • “Exa install auth”
  • “review Exa install auth”
  • “fix Exa install auth”
  • “/exa-install-auth”

Requirements

  • A credential in EXA_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code; live Exa work requires network access
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Inventory the runtime, endpoint family, team, environment, and data class.
  2. Choose exactly one supported authentication model for that boundary.
  3. Place the credential in the approved secret manager and inject it only at runtime.
  4. Pin the current SDK or raw-HTTP contract and validate configuration offline.
  5. Run a synthetic read-only smoke check only when live access and spend are approved.
  6. Record credential owner, scope, rotation path, test result, and rollback state.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • EXA_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; live Exa work requires network access

    From compatibility in the SKILL.md frontmatter.

Context cost

Exa Install Auth loads about 1.2k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 585 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 585 words, ~1,242 tokens.

Download SKILL.mdSave it as .claude/skills/exa-install-auth/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
exa-install-auth
description
Configure an Exa client without leaking credentials or mixing API-key, MCP OAuth, enterprise managed authorization, and payment-protocol trust models. Use when operating or reviewing this Exa boundary. Trigger with "Exa install auth", "review Exa install auth", or "fix Exa install auth".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Designed for Claude Code; live Exa work requires network access
argument-hint
<runtime> <team> <environment>
version
1.12.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, exa
model
inherit
effort
high

Exa Authentication and Installation Boundary

Overview

Configure an Exa client without leaking credentials or mixing API-key, MCP OAuth, enterprise managed authorization, and payment-protocol trust models. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries.

Prerequisites

  • The target repository, environment, Exa team, product surface, and accountable owner.
  • The workload's data classification, latency and freshness promise, cost ceiling, and retention policy.
  • Current first-party documentation plus credentials only for a narrowly approved live check.

Current Contract

The public REST API uses the Exa API host and an Authorization Bearer header. SDKs can read EXA_API_KEY. Team Management uses a separately enabled service key against the admin API; hosted MCP normally uses OAuth, while enterprise managed authorization currently requires an eligible Exa organization, Claude organization, and Okta setup.

Authentication

For normal REST work, inject EXA_API_KEY from an approved server-side secret manager and send it only as Authorization: Bearer to the configured first-party Exa API host. Team Management service keys, hosted MCP OAuth or enterprise managed authorization, and payment-protocol calls are separate trust models. Never print, commit, place in a URL, or expose a credential to an untrusted client.

Instructions

  1. Inventory the runtime, endpoint family, team, environment, and data class.
  2. Choose exactly one supported authentication model for that boundary.
  3. Place the credential in the approved secret manager and inject it only at runtime.
  4. Pin the current SDK or raw-HTTP contract and validate configuration offline.
  5. Run a synthetic read-only smoke check only when live access and spend are approved.
  6. Record credential owner, scope, rotation path, test result, and rollback state.

Tool Discipline

Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. Use Write and Edit only for approved implementation or documentation changes. Do not call Exa, run paid research, create or alter a Monitor, Webset, Agent run, Batch, team, member, API key, budget, webhook, or deployment merely because this skill was invoked.

Approval Boundaries

Require an accountable owner before live queries involving sensitive intent, production credentials, spend or rate-limit changes, forced live crawling, generated summaries, external delivery, deployment, member or key changes, schedule creation, or destructive cancellation, stopping, deletion, or revocation. Read-only repository inspection and synthetic offline validation do not authorize live vendor actions.

Show full SKILL.md (212 more words)Show less

Failure Modes

  • Do not send REST keys in URLs, browser bundles, logs, or client telemetry.
  • A normal API key must not be treated as a Team Management service key.
  • An MCP OAuth session does not authorize unrelated REST or administrative calls.

Output

Return the operation scope, environment, team and product surface, authorization class, contract and policy decisions, deterministic validation results, content-free identifiers, status and cost counts, risks, cleanup or rollback state, and a concise pass or fail receipt. Exclude credentials, raw queries, prompts, presigned URLs, retrieved content, generated output, and customer-derived data unless separately approved.

Example

  • A server worker receives EXA_API_KEY from its production secret store, calls only the approved API host, and reports the request ID without revealing the key.
  • Finish with request or resource IDs, assertion counts, cost and terminal state, rollback or deletion status, and the decision owner; never reproduce secrets or retrieved content.

Validation

Rerun the smallest relevant deterministic test, compare actual behavior with the requested outcome and current first-party contract, verify sensitive fields are absent from evidence, and confirm deadlines, terminal state, downstream retention, and rollback before reporting success.

References

Review the dated first-party evidence map before relying on any endpoint, parameter, search type, price, limit, beta, compliance, identity, retry, or lifecycle claim.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/exa-install-auth of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Exa Install Auth next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Exa Install Auth compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Exa Install Auth this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT
Frontmcp Auth UIagentfront/frontmcp146—~3.7kAutomated safety check: PassApache-2.0
Notion MCP Skillholon-run/uxc116—~1.2kAutomated safety check: PassMIT
Cognitoitsmostafa/aws-agent-skills1.2k1 repos~2.3kAutomated safety check: PassMIT
Auth Implementation Patternsynulihao/AgentSkillOS61810 repos~4.4kAutomated safety check: PassNone
Xquik MCPXquik-dev/x-twitter-scraper2111 repos~997Automated safety check: PassMIT

Similar skills

  • Frontmcp Auth UI

    agentfront/frontmcp

    A skill your agent uses when customizing, branding, or replacing the built-in FrontMCP OAuth pages (the login, consent, federated-select, incremental-authorization, and error pages) with your own…

    146 GitHub stars~3.7k tokensUpdated today
    Backend & APIsAuto-check passed
  • Notion MCP Skill

    holon-run/uxc

    Operate Notion workspace content through Notion MCP using the UXC CLI, including search, fetch, users/teams lookup, page/database creation and updates, and comments.

    116 GitHub stars~1.2k tokensUpdated 26 days ago
    Backend & APIsAuto-check passed
  • Cognito

    itsmostafa/aws-agent-skills

    AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub starsUsed in 1 repo~2.3k tokens
    Backend & APIsAuto-check passed
  • Auth Implementation Patterns

    ynulihao/AgentSkillOS

    Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems.

    618 GitHub starsUsed in 10 repos~4.4k tokens
    Backend & APIsAuto-check passed
  • Xquik MCP

    Xquik-dev/x-twitter-scraper

    Connect, verify, and troubleshoot Xquik's remote MCP server.

    211 GitHub starsUsed in 1 repo~997 tokens
    Backend & APIsAuto-check passed
  • Soundcloud API Auth

    soundcloud/api

    Implements SoundCloud OAuth 2.1 flows — Authorization Code with PKCE and Client Credentials — including token refresh and secure credential storage.

    259 GitHub stars~562 tokensUpdated 10 days ago
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Exa Install Auth

What does Exa Install Auth do?

Configure an Exa client without leaking credentials or mixing API-key, MCP OAuth, enterprise managed authorization, and payment-protocol trust models. Exa Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure an Exa client without leaking credentials or mixing API-key, MCP OAuth, enterprise managed authorization, and payment-protocol trust models.

When should I use Exa Install Auth?

Exa Install Auth fits situations like: reviewing this Exa boundary; with Exa install auth; review Exa install auth; fix Exa install auth.

How do I install Exa Install Auth in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill exa-install-auth -a claude-code`. Or copy the skill folder (skills/.curated/exa-install-auth in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/exa-install-auth in your project. Claude Code loads it when a task matches its description.

How do I install Exa Install Auth in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill exa-install-auth -a codex`. Or copy the skill folder (skills/.curated/exa-install-auth in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/exa-install-auth in your project. Codex loads it when a task matches its description.

Can I use Exa Install Auth in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill exa-install-auth -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exa-install-auth, .gemini/skills/exa-install-auth, .github/skills/exa-install-auth and .opencode/skills/exa-install-auth in your project.

What does Exa Install Auth need to run?

Going by SKILL.md and its folder, Exa Install Auth needs credentials named EXA_API_KEY. Our summary lists: A credential in EXA_API_KEY. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live Exa work requires network access.

Does Exa Install Auth access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Exa Install Auth safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Exa Install Auth use?

Exa Install Auth is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Exa Install Auth use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 459 tokens, read only when the agent opens those files.

What are the alternatives to Exa Install Auth?

Skills that share tags, products or a category with Exa Install Auth: Frontmcp Auth UI (agentfront/frontmcp, 146 stars), Notion MCP Skill (holon-run/uxc, 116 stars), Cognito (itsmostafa/aws-agent-skills, 1.2k stars) and Auth Implementation Patterns (ynulihao/AgentSkillOS, 618 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Exa Install Auth?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.