feedback

Compose and submit identifiers-only product feedback rows to the Powerset feedback API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a search or import skill produces a bad result (wrong person, bad LinkedIn URL, bad ranking, a crash), engineers need enough session context to reproduce the issue, but manually assembling that context is tedious and risks leaking private message content. This Skill mines the current session for repro-relevant identifiers, enforces a strict privacy contract, and files one structured feedback row to Powerset. ## Core Features & Use Cases - Session context mining: Collects the user's verbatim query, the failing command line, JSON payload statuses, run artifacts (decision.json, task-state files, stage manifests), and affected person identifiers from the current conversation without re-running failing commands. - Privacy contract enforcement: Sends identifiers only (names, LinkedIn URLs, UUIDs, counts, statuses) and never message bodies, dossier prose, or machine free-text reasons; person identifiers ship only after explicit user consent via a dry-run preview. - Structured submission: Posts one validated row to the POST /v2/feedback endpoint through the send_feedback primitive, with optional gzip+base64 inline artifact attachments and handling for submitted, needs_auth, and failed outcomes. - Use Case: After a $search run returns the wrong LinkedIn profile, say "report this" and the agent composes a feedback row with the query, decision.json, and the wrong profile's identifiers, previews it, asks about redaction, and submits it. ## Quick Start Report the bad search result from this session to Powerset, previewing the feedback row before sending it.

Frequently Asked Questions about feedback

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

FAQPage Schema
How do I report a bad search result to Powerset?▼

Invoke the feedback skill right after the bad result and it mines the current session for the query, failing command, run artifacts, and affected person identifiers. It then previews the composed row with --dry-run, asks one consent question about person identifiers, and submits via the send_feedback primitive.

What data does the feedback skill send to Powerset?▼

It sends identifiers only: your verbatim query, names, LinkedIn URLs, person UUIDs, run-dir paths, command lines, JSON statuses, counts, and version info. It never sends message bodies, email subjects, dossier prose, or machine free-text reasons.

Can I send feedback without including person names or LinkedIn URLs?▼

Yes. The Step 3 preview asks whether to send with person identifiers, send redacted, or not send. Choosing redacted drops the people array, person-identifying fields, and any artifact that names people before submission.

Why does feedback submission fail with needs_auth?▼

A needs_auth response (exit 3) means the stored Powerset login bearer token is missing or expired. Run the powerset setup flow to sign in again, then retry the submission once.

What are the size limits for feedback artifacts?▼

Keep the whole body under roughly 50 KB; the send_feedback primitive refuses at 900 KB and the server rejects 1 MB. JSON artifacts compress about 5-10x via gzip+base64, so a few MB of raw artifact usually still fits.