Optimized patterns for AI agent workflows, Git integration, MCP servers, and multi-agent orchestration.
Works with
Covers essential commands across Claude, Gemini, and Codex CLIs, plus keyboard shortcuts for task cancellation, history search, and plan mode toggling
Includes session management techniques (resume, rename, aliases) and Git workflows for auto-generating commits, PRs, and managing parallel branches with worktrees
Provides MCP server configuration guidance (Playwright, Supabase, Fire
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionagentic-workflowExecute the skills CLI command in your project's root directory to begin installation:
Fetches agentic-workflow from supercent-io/skills-template 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 agentic-workflow. Access via /agentic-workflow 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
88
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
88
stars
| Command | Function | When to use |
|---|---|---|
/init |
Auto-generate a CLAUDE.md draft | Start a new project |
/usage |
Show token usage/reset time | Start of every session |
/clear |
Clear conversation history | When context is polluted; start a new task |
/context |
Context window X-Ray | When performance degrades |
/clone |
Clone the entire conversation | A/B experiments; backups |
/mcp |
Manage MCP servers | Enable/disable MCP |
!cmd |
Run immediately without Claude processing | Quick status checks |
| Command | Function |
|---|---|
gemini |
Start a conversation |
@file |
Add file context |
-m model |
Select model |
| Command | Function |
|---|---|
codex |
Start a conversation |
codex run |
Run a command |
| Shortcut | Function | Importance |
|---|---|---|
Esc Esc |
Cancel the last task immediately | Highest |
Ctrl+R |
Search prompt history | High |
Shift+Tab x2 |
Toggle plan mode | High |
Tab / Enter |
Accept prompt suggestion | Medium |
Ctrl+B |
Send to background | Medium |
Ctrl+G |
Edit in external editor | Low |
| Shortcut | Function |
|---|---|
Ctrl+A |
Move to start of line |
Ctrl+E |
Move to end of line |
Ctrl+W |
Delete previous word |
Ctrl+U |
Delete to start of line |
Ctrl+K |
Delete to end of line |
# Continue the last conversation
claude --continue
# Resume a specific session
claude --resume <session-name>
# Name the session during the conversation
/rename stripe-integration
# ~/.zshrc or ~/.bashrc
alias c='claude'
alias cc='claude --continue'
alias cr='claude --resume'
alias g='gemini'
alias cx='codex'
"Analyze the changes, write an appropriate commit message, then commit"
"Create a draft PR from the current branch's changes.
Make the title summarize the changes, and list the key changes in the body."
# Work on multiple branches simultaneously
git worktree add ../myapp-feature-auth feature/auth
git worktree add ../myapp-hotfix hotfix/critical-bug
# Independent AI sessions per worktree
Tab 1: ~/myapp-feature-auth → new feature development
Tab 2: ~/myapp-hotfix → urgent bug fix
Tab 3: ~/myapp (main) → keep main branch
1. "Run gh pr checkout 123 and summarize this PR's changes"
2. "Analyze changes in src/auth/middleware.ts. Check for security issues or performance problems"
3. "Is there a way to make this logic more efficient?"
4. "Apply the improvements you suggested and run tests"
| MCP server | Function | Use case |
|---|---|---|
| Playwright | Control web browser | E2E tests |
| Supabase | Database queries | Direct DB access |
| Firecrawl | Web crawling | Data collection |
| Gemini-CLI | Large-scale analysis | 1M+ token analysis |
| Codex-CLI | Run commands | Build, deploy |
# Gemini: large-scale analysis
> ask-gemini "@src/ Analyze the structure of the entire codebase"
# Codex: run commands
> shell "docker-compose up -d"
> shell "npm test && npm run build"
# Disable unused MCP servers
/mcp
# Recommended numbers
# - MCP servers: fewer than 10
# - Active tools: fewer than 80
[Claude] Plan → [Gemini] Analysis/research → [Claude] Write code → [Codex] Run/test → [Claude] Synthesize results
1. [Claude] Design API spec using the skill
2. [Gemini] ask-gemini "@src/ Analyze existing API patterns" - large-scale codebase analysis
3. [Claude] Implement code based on the analysis
4. [Codex] shell "npm test && npm run build" - test and build
5. [Claude] Create final report
"Work using TDD. First write a failing test,
then write code that makes the test pass."
# The AI:
# 1. Write a failing test
# 2. git commit -m "Add failing test for user auth"
# 3. Write minimal code to pass the test
# 4. Run tests → confirm they pass
# 5. git commit -m "Implement user auth to pass test"
FROM ubuntu:22.04
RUN apt-get update && apt-get install -y \
curl git tmux vim nodejs npm python3 python3-pip
RUN curl -fsSL https://claude.ai/install.sh | sh
WORKDIR /workspace
CMD ["/bin/bash"]
# Build and run the container
docker build -t ai-sandbox .
docker run -it --rm \
-v $(pwd):/workspace \
-e ANTHROPIC_API_KEY=$ANTHROPIC_API_KEY \
ai-sandbox
# Do experimental work inside the container
/context # Check usage
/clear # Reset context
# Or create HANDOFF.md and start a new session
Esc Esc # Cancel the last task immediately
# Check MCP/tool counts
/mcp
# Disable unnecessary MCP servers
# Reset context
=== Essential commands ===
/clear reset context
/context check usage
/usage check tokens
/init generate project description file
!command run immediately
=== Shortcuts ===
Esc Esc cancel task
Ctrl+R search history
Shift+Tab×2 plan mode
Ctrl+B background
=== CLI flags ===
--continue continue conversation
--resume resume session
-p "prompt" headless mode
=== Multi-Agent ===
Claude plan/code generation
Gemini large-scale analysis
Codex run commands
=== Troubleshooting ===
Context overloaded → /clear
Cancel task → Esc Esc
Performance degradation → check /context
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.
supercent-io/skills-template
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
Registry listing for agentic-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: agentic-workflow is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: agentic-workflow is focused, and the summary matches what you get after install.
Keeps context tight: agentic-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: agentic-workflow is focused, and the summary matches what you get after install.
I recommend agentic-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
agentic-workflow has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added agentic-workflow from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
agentic-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
agentic-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 69