eve-se-index

incept5/eve-skillpacks · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/incept5/eve-skillpacks --skill eve-se-index
0 commentsdiscussion
summary

Use this skill as the entry point for Eve SE. It routes to the correct skill for the task.

skill.md

Eve SE Index (Load First)

Use this skill as the entry point for Eve SE. It routes to the correct skill for the task.

Scope

Eve SE is for app developers using Eve to deploy and run their apps. It does not cover operating the Eve platform itself.

Quick Routing

Need Load this skill
Full onboarding (new or existing user) eve-bootstrap
Understand Eve CLI primitives eve-cli-primitives
Set up a new project from the starter eve-new-project-setup
Connect an existing repo to Eve (already authed) eve-project-bootstrap
Implement a plan via Eve jobs eve-plan-implementation
Edit the manifest eve-manifest-authoring
Configure auth + secrets eve-auth-and-secrets
Local docker-compose dev loop eve-local-dev-loop
Deploy to staging + debug eve-deploy-debugging
Pipelines + workflows eve-pipelines-workflows
Troubleshoot failures eve-troubleshooting
Keep repo aligned with platform eve-repo-upkeep
Web UI testing with agent-browser eve-web-ui-testing-agent-browser
Author verification plans for an app eve-verification-plans
Design an agent-native app eve-agent-native-design (eve-design pack)

Default Workflow (Local -> Staging)

  1. Run locally with Docker Compose: eve-local-dev-loop.
  2. Ensure manifest matches runtime: eve-manifest-authoring.
  3. Set secrets and auth: eve-auth-and-secrets.
  4. Deploy to staging and debug: eve-deploy-debugging.

What This Pack Does NOT Cover

  • Running Eve Horizon itself (k8s, docker, infra)
  • Platform operator workflows (./bin/eh, cluster secrets)

If you need platform operations, load the private eve-dev pack instead.

how to use eve-se-index

How to use eve-se-index on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add eve-se-index
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/incept5/eve-skillpacks --skill eve-se-index

The skills CLI fetches eve-se-index from GitHub repository incept5/eve-skillpacks and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/eve-se-index

Reload or restart Cursor to activate eve-se-index. Access the skill through slash commands (e.g., /eve-se-index) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

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

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ 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.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.645 reviews
  • Yuki Khanna· Dec 24, 2024

    eve-se-index has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Zara Robinson· Dec 12, 2024

    eve-se-index fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aisha Abbas· Dec 12, 2024

    We added eve-se-index from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ava Kapoor· Dec 8, 2024

    Useful defaults in eve-se-index — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Dhruvi Jain· Dec 4, 2024

    We added eve-se-index from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Oshnikdeep· Nov 23, 2024

    eve-se-index reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Hassan Kapoor· Nov 19, 2024

    Registry listing for eve-se-index matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Yuki Desai· Nov 15, 2024

    Solid pick for teams standardizing on skills: eve-se-index is focused, and the summary matches what you get after install.

  • Ava Sharma· Nov 3, 2024

    I recommend eve-se-index for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Hassan Sharma· Nov 3, 2024

    eve-se-index reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 45

1 / 5