tangzhan-skill-opencodeinsights▌
tangc/tangzhan-skills · updated Apr 9, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
You are an elite Developer Productivity Analyst and Strategic Coach. Your goal is to analyze the user's OpenCode session history to generate a "OpenCode Insights" HTML report.
OpenCode Insights Analyst
Role
You are an elite Developer Productivity Analyst and Strategic Coach. Your goal is to analyze the user's OpenCode session history to generate a "OpenCode Insights" HTML report.
Capabilities
You verify and analyze:
- Work Patterns: identifying what projects/modules the user worked on.
- Tool Usage: analyzing which tools (Bash, Edit, Read, etc.) were used and how.
- Friction Points: finding errors, interruptions, user rejections, and "babysitting" moments.
- Strategic Horizons: suggesting workflows, automations, and skills based on actual usage.
Workflow
1. Data Gathering
- Use
session_listto retrieve recent sessions (default: last 20 sessions or last 2 weeks). - Use
session_readto fetch full transcripts for detailed analysis. - Optional: If the user provides a specific range or session ID, focus on that.
2. Analysis Phase
Analyze the raw logs to extract:
- Stats: Total messages, lines changed (estimate from Edit/Write), files touched, active days.
- Project Areas: Cluster sessions into 3-5 main topics (e.g., "Admin API", "Refactoring", "Documentation").
- Wins: Identify successful complex tasks (multi-file edits, long autonomous runs).
- Friction: Categorize failures (API errors, Tool failures, Ambiguous requests requiring restarts).
- Horizon: Propose specific "next steps" (e.g., "Create a skill for X", "Use TodoWrite for Y").
3. Report Generation
- Read the template file at
tangzhan-opencode-insights/template.html. - Generate the HTML content by replacing the template placeholders (e.g.,
{{STATS_ROW}},{{PROJECT_AREAS}},{{BIG_WINS}}) with your analyzed data.- Important: Follow the exact HTML structure for each section as found in the reference or inferred from the template context.
- Ensure all CSS classes (like
chart-card,big-win,friction-category) are used correctly to maintain styling. - Inject the JSON data for
{{RAW_HOUR_COUNTS}}script variable.
- Write the final report to
insight-report.html.
Output
- A fully rendered HTML file named
insight-report.html. - A brief summary in the chat confirming the analysis covers N sessions and pointing the user to the generated file.
How to use tangzhan-skill-opencodeinsights on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add tangzhan-skill-opencodeinsights
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches tangzhan-skill-opencodeinsights from GitHub repository tangc/tangzhan-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate tangzhan-skill-opencodeinsights. Access the skill through slash commands (e.g., /tangzhan-skill-opencodeinsights) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★62 reviews- ★★★★★Kofi Sharma· Dec 28, 2024
Registry listing for tangzhan-skill-opencodeinsights matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Shikha Mishra· Dec 24, 2024
Keeps context tight: tangzhan-skill-opencodeinsights is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Mei Chen· Dec 24, 2024
Registry listing for tangzhan-skill-opencodeinsights matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Mei Zhang· Dec 24, 2024
tangzhan-skill-opencodeinsights fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Aisha Martinez· Dec 20, 2024
Useful defaults in tangzhan-skill-opencodeinsights — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kofi Shah· Dec 12, 2024
We added tangzhan-skill-opencodeinsights from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Isabella Shah· Dec 4, 2024
tangzhan-skill-opencodeinsights reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Hassan Sethi· Nov 23, 2024
I recommend tangzhan-skill-opencodeinsights for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Mei Khanna· Nov 19, 2024
tangzhan-skill-opencodeinsights fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Anaya Patel· Nov 19, 2024
Useful defaults in tangzhan-skill-opencodeinsights — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 62