Nw Stakeholder Engagement Agent Skill
Demonstration preparation, audience-tailored presentations, feedback collection, and business outcome measurement. Load when preparing demos or measuring business value delivery.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/nWave-ai/nWave --skill nw-stakeholder-engagementThe instruction itself
17 sections, as written by the authorStakeholder Engagement
Demonstration Preparation
Audience Analysis
Tailor presentation content and depth to audience type:
| Audience | Focus | Style | Success Criteria |
|----------|-------|-------|-----------------|
| Executive | Business value, ROI, strategic alignment | High-level outcomes, success metrics, roadmap | Business objective achievement, ROI demonstration |
| Business | Functional capability, process improvement, UX | Feature walkthrough, workflow demo, benefit realization | Requirement satisfaction, process efficiency |
| Technical | Implementation quality, architecture, ops readiness | Technical deep-dive, architecture review, operational metrics | Technical excellence, operational readiness |
Demonstration Script Development
Structure as problem-solution narratives:
- Before state: current pain point with quantitative evidence
- Feature walkthrough: end-to-end workflow with realistic data
- After state: measurable improvement with before/after comparison
- Business impact: translate technical metrics to business outcomes
Preparation Checklist
- [ ] Demo environment set up with realistic data
- [ ] Backup plan for demo failures (screenshots, recorded fallback)
- [ ] Stakeholder briefing sent with agenda and expectations
- [ ] Interactive participation points identified
- [ ] Time budget allocated per section
Feedback Collection
Structured Feedback Process
- Real-time feedback during demonstration (capture questions and concerns)
- Post-demonstration survey with structured questions
- Follow-up interviews for deeper insights (optional, for major features)
Feedback Categories
- Functional: does the feature meet requirements?
- Usability: is the user experience intuitive?
- Performance: does speed/responsiveness meet expectations?
- Priority: what enhancements should come next?
Feedback Action Workflow
- Categorize feedback items
- Prioritize by business impact
- Assign ownership for each action item
- Communicate response plan with timelines
- Track resolution to completion
Business Outcome Measurement
Quantitative Metrics
| Category | Metrics |
|----------|---------|
| Performance | Response time improvement | throughput gains | error rate reduction |
| Business | Revenue impact | cost reduction | user adoption rate | conversion changes |
| Operational | Deployment frequency | MTTR | support ticket reduction | availability |
Qualitative Assessments
User satisfaction surveys (NPS, CSAT) | Usability testing results | Stakeholder satisfaction with delivery quality | Alignment with business objectives.
Success Validation Process
- Baseline: collect pre-implementation measurements
- Monitor: track metrics post-deployment (minimum 2 weeks)
- Validate: compare against success thresholds with statistical rigor
- Report: present results framed in business value terms
- Iterate: identify continuous improvement opportunities
Retrospective and Lessons Learned
Delivery Effectiveness Assessment
Feature delivery timeline vs plan | Quality gate effectiveness (false positives/negatives) | Stakeholder satisfaction scores | Implementation quality metrics.
Knowledge Capture
Successful practices to replicate | Challenges encountered and resolution strategies | Process improvements identified | Tool/technology effectiveness observations.
Integration into Future Iterations
Update process templates and checklists | Share learnings across teams | Adjust estimation models based on actuals | Feed enhancement requests into backlog.
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take nwave-ai/nw-stakeholder-engagement from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.