Unsafe Rust code review and FFI soundness checker for identifying memory safety violations.
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
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
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
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
Submit your Claude Code skill and start earning
epx add zhanghandong/rust-skills --skill unsafe-checkerCompatible with
Supported agents
Triggers on 30+ unsafe patterns including raw pointers, transmute, FFI declarations, uninitialized memory, and missing SAFETY documentation
Provides reference tables for valid unsafe use cases (FFI, low-level abstractions, performance bottlenecks) and common errors with fixes
Covers FFI tooling recommendations (bindgen, cbindgen, PyO3, napi-rs) and deprecated patterns with modern alternatives
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionunsafe-checkerExecute the skills CLI command in your project's root directory to begin installation:
epx add zhanghandong/rust-skills --skill unsafe-checkerFetches unsafe-checker from zhanghandong/rust-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/unsafe-checker
Restart Cursor to activate unsafe-checker. Access via /unsafe-checkerin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
clean-code-principles
asyrafhussin/agent-skills · Productivity · same category
yt-dlp
lwmxiaobei/yt-dlp-skill · Productivity · same category
framer-motion
pproenca/dot-skills · Productivity · same category
prd-to-plan
mattpocock/skills · Productivity · same category
awwwards-landing-page
eng0ai/eng0-template-skills · Productivity · same category
drizzle
lobehub/lobehub · Productivity · same category
Useful defaults in unsafe-checker — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend unsafe-checker for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in unsafe-checker — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend unsafe-checker for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for unsafe-checker matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: unsafe-checker is focused, and the summary matches what you get after install.
Keeps context tight: unsafe-checker is the kind of skill you can hand to a new teammate without a long onboarding doc.
unsafe-checker is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
unsafe-checker has been reliable in day-to-day use. Documentation quality is above average for community skills.
unsafe-checker fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 39