القائمة
List accessible Powerset sets, show the active default set, or set POWERPACKS_DEFAULT_SET_ID so local Powerpacks search primitives inherit the desired set scope.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
The single post-import people-processing workflow and per-person dossier surface. Use for $deep-context, "process/resolve/enrich my contacts", "build deep context", a dossier or identity lookup by name/phone/email, duplicate-person review, LinkedIn self-heal, or the staged people/LinkedIn UI. Builds dossiers for imported people and unresolved Gmail/iMessage/WhatsApp candidates, merges duplicates, asks the user only about uncertain additions, runs one budget-gated lookup for the editable Yes decisions plus eligible wrong-link recovery, verifies found LinkedIns, then realizes the approved network and index.
Add Gmail contacts to your local network. Use for $import-gmail. Sets up msgvault/Gmail (OAuth + authorize), asks which accounts and how many years to sync, syncs mail down, and imports contacts free and locally (shared identity directory only) — unresolved contacts go to a research-candidates pool. No Parallel.ai, no RapidAPI, no index build — identity resolution and indexing happen later in $deep-context. Always reruns the full checklist; overwrites in place.
Add iMessage/WhatsApp contacts to your local network. Use for $import-messages. Sets up access (Full Disk Access + WhatsApp QR), syncs message contacts down, matches them against already-imported LinkedIn/Gmail people (free), and imports matched people plus a research-candidates pool. No LLM calls, no paid research, no index build — identity resolution and indexing happen later in $deep-context. Never uploads to a Powerset set.
Deterministic LinkedIn-only Powerpacks setup. Use for $setup. Steps through update, a supported Powerset workspace or an already-prepared custom Modal workspace, LinkedIn Connections.csv import on Modal, source merge, Modal indexing, and local search-index validation. Always reruns the full checklist; overwrites in place. For Gmail use $import-gmail; for iMessage/WhatsApp use $import-messages.
Bootstrap Powerpacks into this agent from one URL — clone the public repo, install every Powerpacks skill for this harness (Claude Code, Codex, or Pi), initialize the hosted Powerset config when requested, then continue the user's ask in the same session without a restart. Use for "install powerpacks", "download the powerpacks skill", "use powerpacks to set up ...", or "set up my local network search using my Powerset account".
Force-update the canonical Powerpacks checkout to the newest published release and reinstall skills while preserving .powerpacks. Use for $update-powerpacks.
| name | powerset-set |
| description | List accessible Powerset sets, show the active default set, or set POWERPACKS_DEFAULT_SET_ID so local Powerpacks search primitives inherit the desired set scope. |
Use this skill when the user wants to choose, inspect, retrieve, list, switch, or set the active Powerset set for local Powerpacks search.
The skill uses the Powerset Search MCP for set retrieval and name resolution. It only manages local set scope:
POWERPACKS_DEFAULT_SET_ID into the local ignored .envFor $powerset sets use <id|name>, resolve and enter the canonical non-.codex
Powerpacks repo before writing .env:
resolve_powerpacks_root() {
for candidate in "${POWERPACKS_REPO_ROOT:-}" "$PWD" "$HOME/powerpacks" "$HOME/workspace/powerpacks"; do
[[ -n "$candidate" ]] || continue
[[ "$candidate" != *"/.codex/"* ]] || continue
if [[ -d "$candidate/packs" && -f "$candidate/pyproject.toml" ]]; then
printf '%s\n' "$candidate"
return 0
fi
done
return 1
}
repo="$(resolve_powerpacks_root)" || {
echo "No canonical non-.codex Powerpacks repo found. Install/copy Powerpacks to ~/powerpacks first." >&2
exit 1
}
cd "$repo"
For read-only set listing, still prefer the canonical repo when available.
$powerset setup.uv run --project . python packs/powerset/primitives/mcp_install/mcp_install.py status --host all
List sets by calling the Powerset Search MCP list_sets tool directly.
Do not use local SQL or set_scope.py for normal set retrieval.
Show the current default by reading POWERPACKS_DEFAULT_SET_ID from the
local .env, then matching that ID against the MCP list_sets result.
If POWERPACKS_DEFAULT_SET_ID is unset, check legacy
POWERSET_DEFAULT_SET_ID.
Set the default by ID or name:
list_sets<name> or <set_id> against the returned sets.env line. If POWERPACKS_DEFAULT_SET_ID= already
exists, replace that line; otherwise append it. Do not append duplicates.POWERPACKS_DEFAULT_SET_ID=<set_id>
set_id, person_count,
member_count, and sales_nav_account_count from MCP. Only run
resolve_set_operators if the user specifically asks to validate local
TurboPuffer operator scoping.set_id is a Powerset set UUID.operator_ids before applying
TurboPuffer allowed_operator_ids.POWERPACKS_DEFAULT_SET_ID is preferred. POWERSET_DEFAULT_SET_ID is still
accepted as a legacy alias by search primitives..env.