SkillAgentSearch skills...

provider-setup

Reports which delegation CLIs are installed and authenticated, installs missing ones, and stores the result. Use before delegating or when a provider errors.

Install / Use

npx skills add athola/claude-night-market --skill provider-setup

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Category

Operations

Supported Platforms

Universal

Tags

Our assessment of provider-setup

provider-setup scores 85/100 on our quality scale, 550th of 763 Operations skills we index.

Its SKILL.md is 4.6 KB long, well organised into 10 sections with 2 code examples: a solid amount of guidance for an agent.

It has 338 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so provider-setup is actively maintained.
  • Our last check on 2026-11-05 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

provider-setup compared with similar skills

All 4 of these similar skills score higher than provider-setup; compare them before choosing.

SkillScoreStarsUpdatedFormat
provider-setup (this skill)by athola8533857d agoSKILL.md
algorithmic-artby anthropics100177.9k58d agoSKILL.md
pptxby anthropics100177.9k58d agoSKILL.md
prospectingby coreyhaines3110060.1k8d agoSKILL.md
ad-creativeby coreyhaines3110060.1k8d agoSKILL.md

Frequently asked questions

How do I install provider-setup?
Run npx skills add athola/claude-night-market --skill provider-setup. The install tabs above show the steps for each supported agent.
Which AI agents does provider-setup work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is provider-setup safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is provider-setup still maintained?
The repository was last updated about 2 months ago, so provider-setup is actively maintained.

name: provider-setup description: Reports which delegation CLIs are installed and authenticated, installs missing ones, and stores the result. Use before delegating or when a provider errors. alwaysApply: false category: delegation-infrastructure tags:

  • setup
  • providers
  • authentication
  • installation dependencies:
  • delegation-core

Provider Setup

Intent

An operator should be able to ask what this machine can delegate to, get a truthful answer, install what is missing, and have that answer remembered. Before this skill existed, an unconfigured provider surfaced only as a failed delegation, and every call re-derived the same facts by spawning up to sixteen subprocesses.

When To Use

  • Before the first delegation on a new machine
  • When a provider errors out and it is unclear whether the cause is the binary, the credential, or the model
  • When deciding which provider to name in a delegation request

When NOT To Use

  • Choosing between two providers that are both ready (Skill(conjure:delegation-core) routes)
  • Debugging a provider's output rather than its availability

What it reports

scripts/delegation_setup.py probes each registered service and prints a table: binary, version, installed, authenticated, and the fix for each unhealthy row.

python3 scripts/delegation_setup.py --status
python3 scripts/delegation_setup.py --doctor
python3 scripts/delegation_setup.py --available

--available is the short answer: the providers confirmed ready to take work right now.

Installing

Installs come from the provenance map in delegation_executor, which is the only source of install commands. A binary with no recorded provenance raises instead of falling back to a guess, because #655 shipped a service naming a binary that an unaffiliated package publishes.

python3 scripts/delegation_setup.py --install gemini
python3 scripts/delegation_setup.py --all

Every install asks first. Declining is a recorded outcome, not a failure, so --all on a machine where two of eight CLIs are wanted still exits 0.

What is remembered, and what is not

plugins/conjure/scripts/provider_ledger.py writes ~/.claude/hooks/delegation/provider-state.json. What it stores is asymmetric on purpose:

| Fact | Cached | Why | |------|--------|-----| | Installed, version | Yes, under a 6-hour TTL | Cheap to re-derive, stable between runs | | Confirmed credential | As a timestamp, never a boolean | A token expires without touching the binary | | A recorded failure | Clears the confirmation immediately | A stale success must not outlive the credential |

A provider whose credentials live inside its CLI reports auth_checked: false, and that never becomes a confirmation. "We did not look" and "it works" are different claims, and the table keeps them apart.

The file is a cache. A truncated or unreadable ledger loads as empty and costs one round of probes.

What this does not change

Routing still probes live. Delegator.verify_service spawns the version and auth probes on the delegation path as it always did, and the ledger does not short-circuit it.

That is a deliberate boundary, not an unfinished edge. Reading a cached success into the router would send work to a provider whose token expired since the probe, and reading a cached failure into the router would disable a provider for the rest of the TTL after one transient error. The ledger answers an operator's question, "what is set up on this machine", where a six-hour-old answer is useful and a wrong one costs a re-run. The router answers "can this call succeed now", where a wrong answer costs the call.

Wiring the ledger into verify_service needs a failure taxonomy that separates a transient refusal from a revoked credential. That does not exist yet.

Exit Criteria

  • [ ] python3 scripts/delegation_setup.py --status prints one row per registered service with its installed and authenticated state
  • [ ] --available names only providers that are installed, carry a confirmed credential, are inside the TTL, and have no recorded failure
  • [ ] ~/.claude/hooks/delegation/provider-state.json exists after a probe and parses as JSON with "version": 1
  • [ ] An install request for a binary with no provenance entry raises UnverifiedBinaryError instead of running a guessed command
  • [ ] A recorded failure clears any standing auth_confirmed_at, so a provider that starts refusing work leaves --available
  • [ ] A corrupt ledger file loads as empty rather than raising

Related Skills

  • Skill(conjure:delegation-core): the routing this setup feeds
  • Skill(leyline:service-registry): health checks for external services generally

Related Skills

View on GitHub
GitHub Stars338
CategoryOperations
Updated1mo ago
Forks35

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions