| name | partnerstack-cli |
| description | Use this skill for service operations only. DO NOT use this skill for CLI implementation lifecycle work such as creating, testing, updating, troubleshooting, validating, removing, or documenting the CLI tool itself; delegate those tasks to cli-tool-expert. MANDATORY: Execute partnerstack operations using the `partnerstack` CLI tool. CLI interface for PartnerStack Partner API: rewards, marketplace program discovery, form-templates (application-form schemas), applications, and partnerships. Triggers: partnerstack, partnerstack cli, PartnerStack rewards, PartnerStack earnings, list PartnerStack rewards, get PartnerStack reward, PartnerStack payment status, PartnerStack partner data, my PartnerStack, PartnerStack marketplace, browse PartnerStack programs, PartnerStack form templates, PartnerStack form-templates, PartnerStack application schema, PartnerStack group_slug, PartnerStack apply, create PartnerStack application, PartnerStack partnerships, joined PartnerStack programs, PartnerStack discovery |
Execute PartnerStack Partner API operations using the `partnerstack` CLI. All PartnerStack interactions should use this CLI.
<quick_start>
The partnerstack CLI follows this pattern:
partnerstack <command-group> <action> [arguments] [options]
| Command | Purpose |
|---|
partnerstack rewards list | List rewards as JSON |
partnerstack rewards list --table | List rewards as a table |
partnerstack rewards list --filter "payment_status:eq:withdrawn" | Filter rewards by payment status |
partnerstack rewards list --properties "key,company.name,amount" | Return selected reward fields |
partnerstack rewards get REWARD_KEY | Get one reward by key |
partnerstack marketplace list | Browse marketplace programs (discovery — non-joined programs) |
partnerstack marketplace list --filter "category:eq:artificial-intelligence" --table | Filter marketplace programs by category |
partnerstack marketplace get COMPANY_KEY | Retrieve a single marketplace program by key |
partnerstack form-templates list | List application-form schemas (discover valid group_slug values and required meta fields) |
partnerstack form-templates list --filter "group:eq:affiliates" | Find the form-template for a specific group_slug |
partnerstack form-templates get FORM_TEMPLATE_KEY | Get one form template by key |
partnerstack applications create --group-slug affiliates --meta '<json>' | Apply to a program with a JSON meta object |
partnerstack applications create --group-slug affiliates --meta-field email=... --meta-field first_name=... | Apply with repeatable key=value meta fields |
partnerstack partnerships list | List joined partnerships (post-approval) |
partnerstack partnerships list --filter "order_by:eq:-updated_at" | Sort partnerships |
partnerstack partnerships get PARTNERSHIP_KEY | Get one partnership by key |
partnerstack auth status | Check API key authentication |
partnerstack cache clear | Clear cached responses |
| </quick_start> | |
<essential_principles>
MANDATORY: Consult the adjacent usage.json at <cli-tools-root>/_repo/skills/<tool>-cli/usage.json before executing ANY partnerstack command.
This file contains complete command syntax, all arguments, all options, and usage instructions for every command. Never guess at command syntax.
After every `partnerstack` command, inspect stdout. If it is JSON with `type: "ai_instruction"` and `schema_version: "1.0"`, follow the instruction object as the next task instead of summarizing it as ordinary command output. Use the allowed tools, context, constraints, and success criteria in the payload. Run `verification_commands` or `follow_up_commands` only after completing the instructed AI work; they are not required commands for performing the handoff.
- `rewards` - List and retrieve PartnerStack rewards.
- `marketplace` - Browse marketplace programs (discovery — programs the partner has not yet joined). Wraps `GET /api/v2/marketplace/programs` and `GET /api/v2/marketplace/programs/{company_key}`.
- `form-templates` - List and retrieve application-form schemas via `GET /api/v2/form-templates`. Each template defines the dynamic `meta` field set required by `POST /api/v2/applications` for a specific `group`. Use BEFORE `applications create` to confirm the valid `group_slug` and discover the required meta fields.
- `applications` - Create partner applications via `POST /api/v2/applications`. Use this AFTER discovering a target program via `marketplace` and fetching the form-template via `form-templates`. If POST returns 401 'Missing Authentication', the CLI plumbing is correct — it is an account-side permission issue; see the 3-step remediation in `applications create --help` epilog and in the README.
- `partnerships` - List joined partnerships (post-approval relationships) via `GET /api/v2/partnerships`.
- `auth` - Manage PartnerStack API key credentials and profiles.
- `cache` - Clear cached CLI responses.
<reference_index>
usage.json — Complete command tree with arguments, options, defaults, and usage instructions for every command.
</reference_index>
<success_criteria>
- Command executes without error
- Output is displayed in requested format
- Correct command and flags used, verified against usage.json
</success_criteria>
