Use this flow to connect an existing repo to Eve and get the first deploy running.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioneve-project-bootstrapExecute the skills CLI command in your project's root directory to begin installation:
Fetches eve-project-bootstrap from incept5/eve-skillpacks 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 eve-project-bootstrap. Access via /eve-project-bootstrap 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
0
upvotes
Run in your terminal
0
installs
0
this week
—
stars
Use this flow to connect an existing repo to Eve and get the first deploy running.
eve profile create staging --api-url https://api.eh1.incept5.dev
eve profile use staging
eve org ensure my-org --slug myorg
eve project ensure --name "My App" --slug my-app --repo-url [email protected]:me/my-app.git --branch main
URL impact: These slugs determine your deployment URLs and K8s namespaces:
{service}.{orgSlug}-{projectSlug}-{env}.{domain} (e.g., api.myorg-my-app-staging.eh1.incept5.dev)eve-{orgSlug}-{projectSlug}-{env} (e.g., eve-myorg-my-app-staging)Slugs are immutable — choose short, meaningful values.
Set defaults:
eve profile set --org org_xxx --project proj_xxx
.eve/manifest.yaml is present and uses schema: eve/compose/v1.eve-manifest-authoring skill for structure details.# Create environment if needed
eve env create staging --project proj_xxx --type persistent
# Deploy (requires --ref with 40-char SHA or a ref resolved against --repo-dir)
eve env deploy staging --ref main --repo-dir .
# If the environment has a pipeline configured, this triggers the pipeline.
# Use --direct to bypass pipeline and deploy directly:
eve env deploy staging --ref main --repo-dir . --direct
eve system health
eve job list --phase active
eve job follow <job-id>
eve job result <job-id>
Access apps via {service}.{orgSlug}-{projectSlug}-{env}.{domain}.
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
pproenca/dot-skills
mattpocock/skills
Keeps context tight: eve-project-bootstrap is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added eve-project-bootstrap from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: eve-project-bootstrap is the kind of skill you can hand to a new teammate without a long onboarding doc.
eve-project-bootstrap has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in eve-project-bootstrap — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
eve-project-bootstrap is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
eve-project-bootstrap fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
eve-project-bootstrap reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for eve-project-bootstrap matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend eve-project-bootstrap for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 57