Agent skill

Productboard Expert

by borghei in borghei/Claude-Skills

Productboard expert for workspace setup, Insight-to-Feature triage, Driver scoring, Releases, Roadmap views, and REST API automation.

MITAuto-check passedProduct & Project Management

Install Productboard Expert

skills CLI
$ npx skills add borghei/Claude-Skills --skill productboard-expert -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills productboard-expert --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/productboard-expert .claude/skills/productboard-expert && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
productboard-expert
GitHub stars
886
Token cost
~1.9k tokens
SKILL.md length
762 words
Files
9 (incl. references, assets)
Skills in repo
354
Repo updated
First seen
Licence
MIT

At a glance

Productboard expert for workspace setup, Insight-to-Feature triage, Driver scoring, Releases, Roadmap views, and REST API automation.

  • Productboard administration
  • SKILL.md covers Overview, Core Capabilities, When to Use and References, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Prioritization workflows

What it does

Productboard Expert is an agent skill from borghei/Claude-Skills. Productboard expert for workspace setup, Insight-to-Feature triage, Driver scoring, Releases, Roadmap views, and REST API automation. Use for Productboard administration, prioritization workflows, and programmatic API operations.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files and assets (for example `assets/productboard-driver-template.md`, `assets/productboard-feature-template.md` and `assets/productboard-insight-triage-workflow.md`).

It sits in Product & Project Management, covering Prioritization frameworks, REST APIs and Project management. It works with Jira, Intercom and Salesforce. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Productboard administration
  • Prioritization workflows
  • Programmatic API operations

Example prompts

  • “/productboard-expert”

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • developer.productboard.com
    • help.productboard.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Productboard Expert loads about 1.9k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 762 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~19k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 762 words, ~1,930 tokens.

Download SKILL.mdSave it as .claude/skills/productboard-expert/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
productboard-expert
description
Productboard expert for workspace setup, Insight-to-Feature triage, Driver scoring, Releases, Roadmap views, and REST API automation. Use for Productboard administration, prioritization workflows, and programmatic API operations.
license
MIT + Commons Clause
metadata.version
1.0.1
metadata.author
borghei
metadata.category
project-management
metadata.domain
pm-integration
metadata.updated
2026-06-15
metadata.tech-stack
productboard, rest-api, insights, drivers, features, releases
metadata.tags
productboard, prioritization, insights, drivers, roadmap, salesforce, intercom, slack

Productboard Expert

Master-level expertise in Productboard workspace configuration, Insight inbox triage, Driver-based prioritization, Feature hierarchy management, Releases and Roadmap views, REST API operations, and two-way integration with Jira, Linear, Azure DevOps, Salesforce, Intercom, and Slack. Productboard sits between customer-feedback intake (Slack/Intercom/Salesforce/email) and the engineering tracker (Jira/Linear), with an opinionated three-layer model that differs meaningfully from generic issue trackers.

Overview

Productboard separates three layers: Insights (inbound customer evidence), Features (candidate product changes organized in Components and parent/child hierarchy), and Drivers + Releases (the prioritization framework — Drivers = weighted criteria, Releases = time-boxed delivery groupings). Insights link to Features (many-to-many); Features score against Drivers; high-scoring Features get added to Releases; Releases push down to Jira/Linear epics. The flow is inbox → triage → prioritize → ship.

The job of a Productboard expert is to operate fluently inside this model: configure the workspace cleanly, run the Insight inbox without backlog, design Driver weightings that match company strategy, and write API automations for what the UI does not cover.

Core Capabilities

  • Workspace & hierarchy setup — Components, Feature taxonomy, Tags, custom fields, roles
  • Insight inbox triage — the highest-leverage daily ritual; verbatim discipline, multi-Feature linking
  • Driver configuration & Feature scoring — 3-5 weighted Drivers, composite scoring, quarterly re-weighting
  • Releases & Roadmap views — time-boxed delivery, audience-specific views, Portal for customers
  • REST API automation — bulk Insight/Feature operations, webhooks, custom-field updates, pagination
  • Two-way integration — Jira/Linear/Azure DevOps (Features↔Epics) and Salesforce/HubSpot/Intercom/Zendesk (Insight capture)

When to Use

  • Setting up a new Productboard workspace, Component hierarchy, or Feature taxonomy
  • Configuring Drivers and weighting them against strategic objectives
  • Running the Insight inbox triage workflow (the highest-leverage daily ritual)
  • Configuring two-way Jira/Linear/Azure DevOps integration or CRM customer sync
  • Building Roadmap views for executives, customers, and internal teams
  • Writing API calls to bulk-create Insights, update Features, or read prioritization data
  • Migrating from spreadsheet-based prioritization, or troubleshooting "Insights aren't flowing", "scores aren't updating", and similar workflow failures

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/operations-playbook.md — concepts (data model, three layers, Importance×Evidence), all 9 core workflows (setup, triage, Drivers, scoring, Releases, integrations, capture, bulk ops), inline API call catalog, best practices, troubleshooting table, and success criteria. Read this for any setup, triage, scoring, or API task.
  • references/productboard-api-patterns.md — full REST API call catalog with curl examples and JSON shapes. Read when scripting against the API.
  • references/productboard-vs-jira-vs-linear.md — when to use Productboard alongside (or instead of) Jira/Linear; concept translation. Read when positioning the tool in an existing stack.
  • references/red-flags.md — common ways this skill's output goes wrong, with fixes. Read before finalizing a workspace design or prioritization recommendation.
  • Assets: assets/productboard-feature-template.md (Feature structure), assets/productboard-insight-triage-workflow.md (daily triage SOP), assets/productboard-driver-template.md (Driver definitions). Official docs: https://developer.productboard.com/ · https://help.productboard.com/
Show full SKILL.md (331 more words)Show less

Scope & Limitations

In Scope: Workspace and Component hierarchy setup, Insight inbox triage, Driver configuration and Feature scoring, Releases and Roadmap views (internal and customer-facing), Productboard REST API operations (Features, Insights, Releases, custom fields, webhooks), two-way integration setup with Jira/Linear/Azure DevOps, customer-data sync from Salesforce/HubSpot, bulk operations via API, Portal configuration.

Out of Scope: Engineering-side Jira/Linear configuration (see jira-expert/, linear-expert/). Strategic prioritization framework selection (see execution/prioritization-frameworks/). PRD authoring (see execution/create-prd/). Customer interview synthesis (see discovery/interview-synthesis/).

Limitations: API recipes target Public API v2 (/v2/...); v1 (X-Version: 1) was scheduled to sunset on 2026-07-08, and a few v1 capabilities (note followers, feedback forms, company field-definition management) have no v2 equivalent as of September 2026. API rate limits apply per access token (documented default 50 requests/second); aggressive scripts still compete with integrations sharing that token. The Salesforce/HubSpot integration is one-way (CRM → Productboard) on a schedule, not real time. Drivers max out at 10 per workspace on most plans. Roadmap views are good for time-bound delivery (Releases) but weaker for outcome-based roadmaps (Now/Next/Later) — augment with execution/outcome-roadmap/. Per-Component access control is an Enterprise feature.

Integration Points

IntegrationDirectionWhat flows
jira-expert/Productboard ↔ JiraFeatures push as Epics; status flows back; Sprint plan derived from prioritization
linear-expert/Productboard ↔ LinearFeatures push as Projects/Issues; Cycle assignment from Release dates
execution/prioritization-frameworks/BidirectionalDrivers operationalize RICE/ICE/WSJF; external scores import as custom fields
execution/create-prd/Productboard → PRDHigh-priority Features become PRDs; PRD link returns as custom field
execution/outcome-roadmap/BidirectionalOutcome themes map to Objectives; Releases give the delivery side
execution/roadmap-communication/Productboard → CommsCustomer-facing Roadmap variants pull from Portal
execution/customer-feedback-triage/BidirectionalTriaged feedback clusters become Insights; inbox is the triage entry point
execution/release-notes/Productboard → Release NotesCompleted Features in a Release become release-note line items
senior-pm/Productboard → PortfolioDriver scores and Feature distribution feed portfolio health
notion-pm/Productboard ↔ NotionRoadmap embeds into Notion; deep PRDs live in Notion linked from Features
discovery/interview-synthesis/BidirectionalInterview insights become Notes; high-evidence Features motivate interviews
business-growth/customer-success/CS → ProductboardCS is a primary Insight source via Salesforce / Intercom integration

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references, assets) in project-management/productboard-expert of borghei/Claude-Skills.

  • SKILL.md
  • assets/productboard-driver-template.md
  • assets/productboard-feature-template.md
  • assets/productboard-insight-triage-workflow.md
  • examples/wayfinder-productboard-setup.md
  • references/operations-playbook.md
  • references/productboard-api-patterns.md
  • references/productboard-vs-jira-vs-linear.md
  • references/red-flags.md

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Productboard Expert next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Productboard Expert compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Productboard Expert this skillborghei/Claude-Skills886—~1.9kAutomated safety check: PassMIT
Jira Natural Language Interfacejjmartres/opencode1333 repos~1.7kAutomated safety check: PassMIT
Tidycroffasia/itsaplan913—~2.8kAutomated safety check: PassAGPL-3.0
Senior Pmalirezarezvani/claude-skills28k1 repos~4.1kAutomated safety check: PassMIT
JiraRightNow-AI/openfang18k—~694Automated safety check: PassApache-2.0
Pm Skillsalirezarezvani/claude-skills28k—~2.6kAutomated safety check: PassMIT

Similar skills

  • Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.

    133 GitHub starsUsed in 3 repos~1.7k tokens
    Product & Project ManagementAuto-check passed
  • Tidy

    croffasia/itsaplan

    Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality.

    913 GitHub stars~2.8k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Senior Pm

    alirezarezvani/claude-skills

    Senior Project Manager for enterprise software, SaaS, and digital transformation projects.

    28k GitHub starsUsed in 1 repo~4.1k tokens
    Product & Project ManagementAuto-check passed
  • Jira

    RightNow-AI/openfang

    Jira project management expert for issues, sprints, workflows, and reporting

    18k GitHub stars~694 tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check passed
  • Pm Skills

    alirezarezvani/claude-skills

    A skill your agent uses when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin…

    28k GitHub stars~2.6k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Product Roadmap

    tikalk/adlc-team-skills

    A skill your agent uses when doing weekly progress checks or milestone validation — tracks decision, execution, evidence, and gate states across four layers of truth.

    141 GitHub stars~3.1k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from borghei/Claude-Skills

All 354 skills in this repo
  • Agent Harness

    borghei/Claude-Skills

    Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.

    886 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    886 GitHub stars~4.2k tokensUpdated 2 days ago
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    886 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    886 GitHub stars~3.6k tokensUpdated 2 days ago
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    886 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    886 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Productboard Expert

What does Productboard Expert do?

Productboard expert for workspace setup, Insight-to-Feature triage, Driver scoring, Releases, Roadmap views, and REST API automation. Productboard Expert is an agent skill from borghei/Claude-Skills. Productboard expert for workspace setup, Insight-to-Feature triage, Driver scoring, Releases, Roadmap views, and REST API automation.

When should I use Productboard Expert?

Productboard Expert fits situations like: productboard administration; prioritization workflows; programmatic API operations.

How do I install Productboard Expert in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill productboard-expert -a claude-code`. Or copy the skill folder (project-management/productboard-expert in borghei/Claude-Skills) into .claude/skills/productboard-expert in your project. Claude Code loads it when a task matches its description.

How do I install Productboard Expert in Codex?

Run `npx skills add borghei/Claude-Skills --skill productboard-expert -a codex`. Or copy the skill folder (project-management/productboard-expert in borghei/Claude-Skills) into .agents/skills/productboard-expert in your project. Codex loads it when a task matches its description.

Can I use Productboard Expert in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill productboard-expert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/productboard-expert, .gemini/skills/productboard-expert, .github/skills/productboard-expert and .opencode/skills/productboard-expert in your project.

What does Productboard Expert need to run?

SKILL.md names no scripts, command-line tools or credentials: Productboard Expert is instructions for the agent only.

Does Productboard Expert access the network?

SKILL.md names 2 domains. As links in the text: developer.productboard.com and help.productboard.com. This is read from the text; nothing was executed.

Is Productboard Expert safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Productboard Expert use?

Productboard Expert is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Productboard Expert use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.

What are the alternatives to Productboard Expert?

Skills that share tags, products or a category with Productboard Expert: Jira Natural Language Interface (jjmartres/opencode, 133 stars), Tidy (croffasia/itsaplan, 913 stars), Senior Pm (alirezarezvani/claude-skills, 28k stars) and Jira (RightNow-AI/openfang, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Productboard Expert?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.