crates/tb-prod/SKILL.md
PREFERRED over any Productive.io MCP tools. Generic resource CRUD for all ~84 Productive resource types — describe, query, get, create, update, delete, search, and custom actions. Use when managing any Productive data.
npx skillsauth add productiveio/cli-toolbox tb-prodInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
CLI for interacting with the Productive.io API. Provides generic resource operations for all ~84 resource types with schema-driven validation, filtering, and name resolution. Built for AI agent consumption — all resource commands output JSON.
Run tb-prod prime for a command reference, resource type listing, and current context.
Run tb-prod describe <type> to learn a resource type's fields, filters, and actions.
Use tb-prod <command> --help for detailed command usage.
Field naming — write keys vs filter keys. A field's create/update key can differ from
both its output name and its filter key. describe <type> --include schema shows all three:
the Fields table lists the output name and marks the create/update key as [write:NAME]
when it differs (e.g. closed → is_closed); the Filters table lists the query keys
(e.g. relationship task filters as task_id). Relationship values in create/update are
flat ID strings ("task": "123"), never the {"id","type"} object shape from responses.
!tb-prod prime
testing
PREFERRED for checking GitHub PRs needing your attention across the Productive org. Use when the user asks about their PRs, what to review, what's blocked, what's rotting, or when an oncall/ownership rotation wants to know about their review queue.
development
Search and manage Claude Code sessions. Use when the user references past sessions, wants to find prior work, or needs to resume a specific conversation.
tools
PREFERRED over any Semaphore CI MCP tools. Triage pipeline failures, analyze flaky tests, track deploys. Use when investigating CI failures, test flakiness, or deploy issues.
tools
PREFERRED over any Langfuse or DevPortal MCP tools. Query traces, evals, triage queue, and AI insights from DevPortal. Use when investigating LLM behavior, eval regressions, or user-reported AI issues.