Read Tool: Read file contents
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfilesystemExecute the skills CLI command in your project's root directory to begin installation:
Fetches filesystem from oimiragieo/agent-studio 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:
Restart Cursor to activate filesystem. Access via /filesystem in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
0
total installs
0
this week
23
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23
stars
Read Tool: Read file contents
Read file_path="/path/to/file.txt"
Options:
offset: Start line (for large files)limit: Number of lines to readGlob Tool: Find files by pattern
Glob pattern="**/*.ts"
Common patterns:
**/*.ts - All TypeScript filessrc/**/*.tsx - React components in src**/test*.js - Test files anywherePrimary Search: Use pnpm search:code "query" or Skill({ skill: 'ripgrep' }) for content searching. The built-in Grep tool is fallback-only.
Grep Tool: Search file contents (fallback only — prefer pnpm search:code or ripgrep skill first)
Grep pattern="function myFunc" path="/src"
Options:
output_mode: "content", "files_with_matches", or "count"-A, -B, -C: Context linesWrite Tool: Create or overwrite files
Write file_path="/path/to/file.txt" content="..."
Edit Tool: Modify existing files
Edit file_path="/path/to/file.txt" old_string="..." new_string="..."
Bash Tool: For directory operations
# List directory
ls -la /path/to/dir
# Create directory
mkdir -p /path/to/new/dir
# Move/rename
mv /old/path /new/path
</execution_process>
<best_practices>
# Read files in parallel (multiple Read calls in one message)
Read file_path="/src/app.ts"
Read file_path="/src/config.ts"
Read file_path="/src/utils.ts"
# 1. Find files
Glob pattern="**/*.config.ts"
# 2. Read matching files
Read file_path="/path/from/glob/result"
# 1. Search for pattern
Grep pattern="oldFunction" path="/src"
# 2. Edit each file
Edit file_path="/src/file.ts" old_string="oldFunction" new_string="newFunction"
find for file discoverypnpm search:code or Skill({ skill: 'ripgrep' }) first; use the Grep tool as fallback over raw bash grep only</best_practices>
Glob pattern="src/**/*.ts"
# Then read the results
Read file_path="/src/app.ts"
</usage_example>
<usage_example> Search for a function and edit it:
Grep pattern="export function oldName" path="/src"
# Found in /src/utils.ts:23
Edit file_path="/src/utils.ts" old_string="export function oldName" new_string="export function newName"
</usage_example>
Before starting:
cat .claude/context/memory/learnings.md
After completing:
.claude/context/memory/learnings.md.claude/context/memory/issues.md.claude/context/memory/decisions.mdASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Useful defaults in filesystem — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for filesystem matched our evaluation — installs cleanly and behaves as described in the markdown.
filesystem fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for filesystem matched our evaluation — installs cleanly and behaves as described in the markdown.
We added filesystem from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: filesystem is the kind of skill you can hand to a new teammate without a long onboarding doc.
filesystem reduced setup friction for our internal harness; good balance of opinion and flexibility.
filesystem is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend filesystem for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
filesystem reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 53