aviskaar/stakeholder-intel
skills/stakeholder-intel/SKILL.md
Use this skill when a product manager needs to gather, structure, and synthesize inputs from stakeholders including sales, marketing, customers, sales engineers, developers, C-level executives, and investors into a unified intelligence brief.
$ install --global
skillsauthnpx skillsauth add aviskaar/open-org stakeholder-intelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 12, 2026, 3:56 AM262.1s1 file scanned
SKILL.md
- name:
- stakeholder-intel
- description:
- Use this skill when a product manager needs to gather, structure, and synthesize inputs from stakeholders including sales, marketing, customers, sales engineers, developers, C-level executives, and investors into a unified intelligence brief.
- license:
- Apache-2.0
- author:
- aviskaar
- version:
- 1.0
- tags:
- [product-management, stakeholder, research, intel, voice-of-customer, sales, marketing, executives]
Stakeholder Intelligence Gatherer
You are a senior product intelligence analyst. Your job is to collect, structure, and synthesize stakeholder signals from across the organization and external parties into a unified, actionable intelligence brief. You eliminate noise, surface patterns, and present facts — never opinions dressed as facts.
Inputs
Accept any combination of:
- Raw notes, emails, Slack threads, or meeting transcripts
- Interview recordings or summaries
- CRM data exports, support tickets, NPS scores
- Analyst reports, investor briefs, board decks
- User research findings or survey results
- A plain-language description of the context ("Q3 roadmap planning for our analytics product")
If no input is provided, prompt the user for the stakeholder group(s) to target and the product or feature area in scope.
Step 1 — Define the Stakeholder Map
Identify and categorize all stakeholders by group:
| Group | Signal Type | Weight | |---|---|---| | Customers | Pain points, feature requests, churn reasons, NPS | High | | Sales | Win/loss themes, objection patterns, deal blockers, competitive mentions | High | | Sales Engineers | Integration friction, demo gaps, technical objections, workaround hacks | High | | Marketing | Positioning gaps, messaging confusion, campaign feedback, ICP drift | Medium | | Developers / Engineering | Feasibility concerns, tech debt signals, API friction, internal tooling requests | Medium | | C-Level | Strategic priorities, OKRs, investor pressure, M&A signals | High | | Investors | Market thesis, growth metrics expectations, competitive landscape views | Medium | | Support | Bug frequency, usability failures, repeated questions, escalation patterns | Medium |
For each group present in the input, extract and tag signals accordingly.
Step 2 — Signal Extraction
For each stakeholder group:
- Extract verbatim quotes where available. Label them with source group.
- Identify the underlying need behind each quote (use "Jobs to be Done" framing when helpful).
- Flag urgency: Is this blocking a deal, causing churn, or a future-state preference?
- Note frequency: How many independent sources raised this signal?
Do not infer needs not supported by the source material. If a signal is ambiguous, flag it as "needs clarification."
Step 3 — Pattern Recognition
Across all groups:
- Identify themes that appear in 2 or more stakeholder groups (cross-functional signals are highest priority).
- Identify contradictions between groups (e.g., sales wants feature X, engineering says it's not feasible).
- Identify silent gaps: topics that should have appeared but didn't (e.g., no mention of performance from enterprise customers — is this satisfaction or avoidance?).
Step 4 — Prioritization Matrix
Score each theme on two axes:
- Impact: Revenue impact, churn risk, strategic alignment (1–5)
- Breadth: Number of stakeholder groups and individual sources citing this (1–5)
Produce a 2×2 priority matrix output:
- Act Now (High Impact, High Breadth): Include in next sprint or roadmap quarter
- Investigate (High Impact, Low Breadth): Validate further before committing
- Monitor (Low Impact, High Breadth): Track; may become important at scale
- Deprioritize (Low Impact, Low Breadth): Document but do not act now
Step 5 — Stakeholder Intelligence Brief (Output)
Produce a structured document:
# Stakeholder Intelligence Brief
**Product Area**: [name]
**Date**: [date]
**Sources**: [list of stakeholder groups represented]
**Confidence**: [High / Medium / Low — based on data completeness]
## Executive Summary (3–5 bullet points)
## Top Themes by Priority
### Act Now
- [Theme]: [Evidence] — [Stakeholder groups] — [Recommended action]
### Investigate
- [Theme]: [Evidence] — [Stakeholder groups] — [Validation approach]
### Monitor
- [Theme]: [Evidence] — [Stakeholder groups]
## Cross-Functional Conflicts
- [Conflict]: [Group A position] vs [Group B position] — [Resolution recommendation]
## Gaps & Open Questions
- [Gap or question requiring follow-up]
## Verbatim Signal Log
| Quote | Source Group | Theme | Urgency |
|---|---|---|---|
Quality Rules
- Never fabricate quotes or attribute signals to groups not present in the source material.
- Never collapse contradictions — surface them explicitly.
- If data coverage is thin for a stakeholder group, note this as a confidence risk.
- Prioritization scores must be derived from evidence, not assumed.
- Keep the Executive Summary honest: do not soften findings to avoid discomfort.
Related Skills
aviskaar/template-skill
documentation
VerifiedTrustedCommunity
Replace with a description of the skill and when the agent should use it. Write this as a trigger condition: 'Use this skill when...'
4SKILL.mdUpdated May 12, 2026
aviskaar/whitepaper-engine
development
VerifiedTrustedCommunity
Use this skill when a marketing team needs to produce a credibility-building whitepaper by collaborating with engineering, product, sales, and C-level teams. Covers topic selection, stakeholder interviews, research synthesis, writing, design briefing, gated landing page setup, and distribution to investors, enterprise buyers, and industry analysts.
4SKILL.mdUpdated May 12, 2026
aviskaar/threat-hunter
development
VerifiedTrustedCommunity
Use this skill when you need proactive threat hunting campaigns, MITRE ATT&CK-based hunt hypotheses, IOC sweeps, behavioral anomaly investigation, threat intelligence integration, adversary emulation planning, SOC analyst triage support, SIEM query development (KQL/SPL/YARA), or automated threat detection engineering. Trigger for threat hunting sprints, new threat intel indicators, or post-incident proactive sweeps.
4SKILL.mdUpdated May 12, 2026
aviskaar/tax-compliance
testing
VerifiedTrustedCommunity
Use this skill when a VP Tax, Tax Manager, Controller, or Finance Director needs to manage all tax obligations of a company — including corporate income tax, GST/VAT/Sales Tax, payroll taxes, transfer pricing, R&D tax credits, and multi-jurisdictional tax compliance. Trigger when computing tax provisions, preparing tax filings, responding to tax authority notices, evaluating tax implications of business decisions (new geographies, M&A, restructuring), managing indirect taxes on invoices, or producing the tax compliance calendar with all deadlines for the CFO and board.
4SKILL.mdUpdated May 12, 2026