Keep an app repo current with Eve conventions. The checks are independent — run them in parallel when multiple areas need attention.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioneve-repo-upkeepExecute the skills CLI command in your project's root directory to begin installation:
Fetches eve-repo-upkeep 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-repo-upkeep. Access via /eve-repo-upkeep 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
Keep an app repo current with Eve conventions. The checks are independent — run them in parallel when multiple areas need attention.
Quickly determine which areas need attention. Check which of these files exist and whether they look stale — don't deep-read every file, just note which areas need work:
.eve/manifest.yaml — does it exist? Is the schema line eve/compose/v1?skills.txt — does it exist? Are there pinned or obsolete entries?AGENTS.md / CLAUDE.md — do they reference current skills?agents/ directory — do agents.yaml, teams.yaml, chat.yaml exist?If only one area needs work, handle it directly. Otherwise, proceed to Phase 2.
Create one worker per area that needs updating. Each worker description below is self-contained — a worker can execute its area independently without context from the others.
Check and fix .eve/manifest.yaml:
schema: eve/compose/v1 is present.services: over legacy components:.x-eve ingress and pipeline definitions accurate.x-eve.defaults in sync with harness defaults (harness/profile/options).x-eve.agents profiles aligned with orchestration policy.x-eve.agents.config_path and x-eve.chat.config_path point to valid files.${secret.KEY} usage for secrets.build step before release.build.context defined.REGISTRY_USERNAME + REGISTRY_PASSWORD) are required only for custom BYO registries.Check and fix skills.txt:
Check and fix AGENTS.md, CLAUDE.md, and agents/ config files:
eve-se-index.agents/agents.yaml defines agents and skills — verify entries are current.agents/teams.yaml defines team composition and dispatch — verify structure.agents/chat.yaml defines chat routing rules and permissions — verify rules.Search the codebase for deprecated patterns and fix or flag them:
eve deploy vs eve env deploy)--ref parameterorg.opencontainers.image.source label pointing to the repo URLbuild step before releasebuild.context configurationREGISTRY_USERNAME, REGISTRY_PASSWORD or provider-equivalent names)After all workers complete, run final verification:
# Local validation (Docker Compose)
docker compose up --build
# Staging deploy (requires --ref with 40-char SHA or a ref resolved against --repo-dir)
eve env deploy staging --ref main --repo-dir .
# Use --direct to bypass pipeline if needed
eve env deploy staging --ref main --repo-dir . --direct
Track the deploy job with eve job follow.
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
Registry listing for eve-repo-upkeep matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: eve-repo-upkeep is the kind of skill you can hand to a new teammate without a long onboarding doc.
eve-repo-upkeep is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
eve-repo-upkeep reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for eve-repo-upkeep matched our evaluation — installs cleanly and behaves as described in the markdown.
eve-repo-upkeep fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: eve-repo-upkeep is focused, and the summary matches what you get after install.
I recommend eve-repo-upkeep for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
eve-repo-upkeep reduced setup friction for our internal harness; good balance of opinion and flexibility.
eve-repo-upkeep is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 37