powerset

Manages Powerset authentication, runtime key provisioning, MCP registration, and default set selection.

1|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/powerset-co/powerpacks --skill powerset-powerset-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: powerset
Source: https://github.com/powerset-co/powerpacks/tree/main/packs/powerset/skills/powerset
Command: npx skills add https://github.com/powerset-co/powerpacks --skill powerset-powerset-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a Powerset-backed recruiting-search workstation requires juggling Auth0 login, runtime API keys (Modal, OpenAI, Parallel, Powerset), MCP server registration, and default set selection across multiple commands. This Skill unifies all of that into a single $powerset command surface with terse, actionable output. ## Core Features & Use Cases - One-command setup: $powerset setup performs Auth0 login, pulls provisioned runtime keys into .env, and installs the powerset-search MCP in one flow. - Credential and environment management: $powerset login, $powerset status, $powerset whoami, and $powerset env pull keep Auth0 credentials and Modal/OpenAI/Parallel/Powerset API keys current. - Set and MCP administration: $powerset sets list / sets use resolve Powerset sets via the Search MCP and write POWERPACKS_DEFAULT_SET_ID to .env; $powerset mcp install registers or refreshes the MCP for local hosts. - Use Case: A new user on Codex runs $powerset setup, completes the browser Auth0 login, and immediately has runtime keys and the Powerset Search MCP configured without touching config files manually. ## Quick Start Ask your agent to run $powerset setup to log in, pull runtime keys, and install the Powerset MCP in one step.

Frequently Asked Questions about powerset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Powerset for the first time?▼

Run $powerset setup from the canonical Powerpacks repo. It performs Auth0 login, pulls your provisioned Modal, OpenAI, Parallel, and Powerset API keys into .env, and installs the powerset-search MCP in one flow.

How do I pull Powerset runtime API keys into my local .env file?▼

Run $powerset env pull after logging in with Auth0. It fetches MODAL_TOKEN_ID/SECRET, OPENAI_API_KEY, PARALLEL_API_KEY, and POWERSET_API_KEY from the Powerset API and writes them to .env, refreshing existing keys.

Why does $powerset env pull report not_provisioned?▼

The not_provisioned response means an admin must provision the missing runtime key for your Powerset user out of band. The API endpoints never mint keys themselves, so contact your administrator and re-run the pull afterward.

How do I set a default Powerset set for local search?▼

Run $powerset sets use <id-or-name>. The skill lists sets via the Powerset Search MCP, resolves your input against set IDs and names, and writes POWERPACKS_DEFAULT_SET_ID to your local .env file.

Can I check my Powerset setup without changing anything?▼

Yes, run $powerset status for a read-only setup check that summarizes only blockers, or $powerset whoami to show your current Auth0 identity and role. Neither command writes to .env or modifies MCP config.