bear-notes▌
steipete/clawdis · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Use grizzly to create, read, and manage notes in Bear on macOS.
Bear Notes
Use grizzly to create, read, and manage notes in Bear on macOS.
Requirements
- Bear app installed and running
- For some operations (add-text, tags, open-note --selected), a Bear app token (stored in
~/.config/grizzly/token)
Getting a Bear Token
For operations that require a token (add-text, tags, open-note --selected), you need an authentication token:
- Open Bear → Help → API Token → Copy Token
- Save it:
echo "YOUR_TOKEN" > ~/.config/grizzly/token
Common Commands
Create a note
echo "Note content here" | grizzly create --title "My Note" --tag work
grizzly create --title "Quick Note" --tag inbox < /dev/null
Open/read a note by ID
grizzly open-note --id "NOTE_ID" --enable-callback --json
Append text to a note
echo "Additional content" | grizzly add-text --id "NOTE_ID" --mode append --token-file ~/.config/grizzly/token
List all tags
grizzly tags --enable-callback --json --token-file ~/.config/grizzly/token
Search notes (via open-tag)
grizzly open-tag --name "work" --enable-callback --json
Options
Common flags:
--dry-run— Preview the URL without executing--print-url— Show the x-callback-url--enable-callback— Wait for Bear's response (needed for reading data)--json— Output as JSON (when using callbacks)--token-file PATH— Path to Bear API token file
Configuration
Grizzly reads config from (in priority order):
- CLI flags
- Environment variables (
GRIZZLY_TOKEN_FILE,GRIZZLY_CALLBACK_URL,GRIZZLY_TIMEOUT) .grizzly.tomlin current directory~/.config/grizzly/config.toml
Example ~/.config/grizzly/config.toml:
token_file = "~/.config/grizzly/token"
callback_url = "http://127.0.0.1:42123/success"
timeout = "5s"
Notes
- Bear must be running for commands to work
- Note IDs are Bear's internal identifiers (visible in note info or via callbacks)
- Use
--enable-callbackwhen you need to read data back from Bear - Some operations require a valid token (add-text, tags, open-note --selected)
How to use bear-notes 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 bear-notes
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches bear-notes from GitHub repository steipete/clawdis 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 bear-notes. Access the skill through slash commands (e.g., /bear-notes) 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★★★★★43 reviews- ★★★★★Emma Choi· Dec 12, 2024
Registry listing for bear-notes matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ira Lopez· Dec 8, 2024
bear-notes fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Mia Abbas· Nov 27, 2024
We added bear-notes from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Mia Rahman· Nov 3, 2024
Solid pick for teams standardizing on skills: bear-notes is focused, and the summary matches what you get after install.
- ★★★★★Mia Khan· Oct 22, 2024
We added bear-notes from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Mia Ramirez· Oct 18, 2024
Solid pick for teams standardizing on skills: bear-notes is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Sep 25, 2024
Keeps context tight: bear-notes is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ama Martin· Sep 25, 2024
I recommend bear-notes for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ishan Jain· Sep 17, 2024
bear-notes has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chaitanya Patil· Sep 1, 2024
bear-notes reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 43