Search and analyze your complete conversation history using jq and rg.
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 steipete/clawdis --skill session-logsCompatible with
Supported agents
Session logs stored as append-only JSONL files at ~/.openclaw/agents/<agentId>/sessions/ , indexed by session ID with full message transcripts including role, timestamp, content type, and token cost
Extract user messages, assistant responses, tool calls, and metadata using jq filters; search across all sessions or within specific files using rg for keyword matching
Common patterns provided for listing session
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsession-logsExecute the skills CLI command in your project's root directory to begin installation:
epx add steipete/clawdis --skill session-logsFetches session-logs from steipete/clawdis 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/session-logs
Restart Cursor to activate session-logs. Access via /session-logsin 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.
premortem
parcadei/continuous-claude-v3 · Productivity · same category
framer-motion
pproenca/dot-skills · Productivity · same category
nestjs-best-practices
kadajett/agent-nestjs-skills · Productivity · same category
cmux-browser
manaflow-ai/cmux · Productivity · same category
electron-best-practices
jwynia/agent-skills · Productivity · same category
pine-developer
traderspost/pinescript-agents · Productivity · same category
I recommend session-logs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in session-logs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
session-logs has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend session-logs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
session-logs reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in session-logs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
session-logs reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend session-logs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
session-logs has been reliable in day-to-day use. Documentation quality is above average for community skills.
session-logs fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 41