cninfo-to-notebooklm▌
jarodise/cninfo2notebookllm · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Download annual and periodic reports for China A-share and Hong Kong stocks from cninfo.com.cn and upload them to NotebookLM for AI-powered analysis with a specialized "Financial Analyst" persona.
CNinfo to NotebookLM
Overview
Download annual and periodic reports for China A-share and Hong Kong stocks from cninfo.com.cn and upload them to NotebookLM for AI-powered analysis with a specialized "Financial Analyst" persona.
When to Use
- User provides a China stock name or code (A-share or Hong Kong)
- User wants to analyze a company's financial reports
- User asks to "download reports" or "research" a Chinese stock
- User wants to upload stock reports to NotebookLM
Supported Markets
| Market | Code Pattern | Examples |
|---|---|---|
| A-share | 6-digit codes (0xxxxx, 3xxxxx, 6xxxxx) | 600519 (贵州茅台), 000001 (平安银行) |
| Hong Kong | 5-digit codes (00xxx, 01xxx, 02xxx, 09xxx) | 00700 (腾讯控股), 09988 (阿里巴巴) |
Core Workflow
User provides stock name/code
↓
1. Look up stock in database (auto-detect market)
↓
2. Download reports from cninfo:
- Last 5 years annual reports (年度报告)
- Current year: Q1, semi-annual, Q3 reports
↓
3. Create NotebookLM notebook
↓
4. Configure "Financial Analyst" persona with custom prompt
↓
5. Upload all PDFs as sources
↓
6. Return notebook ID ✅
Step-by-Step Instructions
Step 0: Environment Setup (First Run Only)
Crucial: Before running the script, verify the environment is ready.
-
Check Dependencies: Verify if the dependencies are installed (specifically
notebooklmandplaywright). -
Install: If dependencies are missing or this is the first run, execute the installation script:
chmod +x install.sh && ./install.sh -
Authenticate: Ensure the user has authenticated with NotebookLM (
notebooklm login). If not, ask them to do so.
Step 1: Run Main Orchestration Script
Run the script from the skill directory:
python3 scripts/run.py <stock_code_or_name>
Examples:
python3 scripts/run.py 600350- A-share stockpython3 scripts/run.py 山东高速- A-share by namepython3 scripts/run.py 00700- Hong Kong stock (Tencent)python3 scripts/run.py 腾讯控股- Hong Kong by name
This script handles everything:
- Downloads reports to a temp directory.
- Creates a NotebookLM notebook.
- Configures the notebook with
assets/financial_analyst_prompt.txt. - Uploads all PDFs.
- Cleans up temp files.
Step 2: Report to User
Provide:
- ✅ Number of reports downloaded & uploaded
- 📚 NotebookLM notebook ID
- 📊 Market type (A-share or Hong Kong)
- 💡 Remind user the notebook creates a "Financial Analyst" persona for deep analysis.
Configuration
The skill uses a custom system prompt located at:
assets/financial_analyst_prompt.txt
This prompt configures NotebookLM to act as a "Financial Report Analyst" based on "Hand-holding Financial Reporting" methodology.
Error Handling
| Error | Solution |
|---|---|
| Stock not found | Check if code is valid A-share or Hong Kong stock |
| NotebookLM CLI not found | Ensure notebooklm-py matches requirements.txt and is in PATH |
| Auth missing | Run notebooklm login to authenticate via browser |
| Upload failed | Check network connection and NotebookLM service status |
Dependencies
- Python 3.8+
httpxpackagenotebooklm-pypackageplaywright(for authentication)
Quick Reference
A-share Report Types
| Report Type | Category Code | Period |
|---|---|---|
| Annual | category_ndbg_szsh |
Previous 5 years |
| Semi-Annual | category_bndbg_szsh |
Current year |
| Q1 Report | category_yjdbg_szsh |
Current year |
| Q3 Report | category_sjdbg_szsh |
Current year |
Hong Kong Stock Differences
| Aspect | A-share | Hong Kong |
|---|---|---|
| Market code | szse |
hke |
| Categories | Uses category codes | Empty categories |
| Search key | Uses Chinese search terms | Empty search key |
| Report naming | YYYY年年度报告 |
May use Arabic/Chinese numerals |
| Search period | Following year (March-June) | Same year or following year |
How to use cninfo-to-notebooklm 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 cninfo-to-notebooklm
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches cninfo-to-notebooklm from GitHub repository jarodise/cninfo2notebookllm 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 cninfo-to-notebooklm. Access the skill through slash commands (e.g., /cninfo-to-notebooklm) 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.4★★★★★51 reviews- ★★★★★Shikha Mishra· Dec 24, 2024
cninfo-to-notebooklm reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Daniel Tandon· Dec 24, 2024
cninfo-to-notebooklm has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Meera Haddad· Dec 8, 2024
Useful defaults in cninfo-to-notebooklm — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kwame Bansal· Nov 27, 2024
Registry listing for cninfo-to-notebooklm matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Yash Thakker· Nov 15, 2024
I recommend cninfo-to-notebooklm for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Mateo Bansal· Nov 15, 2024
cninfo-to-notebooklm fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Sakshi Patil· Nov 11, 2024
cninfo-to-notebooklm is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Noor Johnson· Oct 18, 2024
cninfo-to-notebooklm reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Dhruvi Jain· Oct 6, 2024
Useful defaults in cninfo-to-notebooklm — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kwame Malhotra· Oct 6, 2024
We added cninfo-to-notebooklm from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 51