Build applications where agents are first-class citizens — not afterthoughts.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioneve-agent-native-designExecute the skills CLI command in your project's root directory to begin installation:
Fetches eve-agent-native-design 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-agent-native-design. Access via /eve-agent-native-design 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
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
0
upvotes
Run in your terminal
0
installs
0
this week
—
stars
Build applications where agents are first-class citizens — not afterthoughts.
Load this skill when:
Every user action must have an agent-equivalent path.
On Eve: The CLI IS the parity layer. If a user can do it through eve ..., an agent can too. When building your app, apply the same principle:
| Check | How |
|---|---|
| Can agents create/read/update/delete every entity? | Map UI actions to CLI/API equivalents |
| Are there UI-only workflows? | Expose them as API endpoints or CLI commands |
| Can agents discover what's available? | Provide list operations for every entity type |
CRUD Completeness: For every entity in your app, verify agents have Create, Read, Update, and Delete paths. Missing any one breaks parity.
Features emerge from agent loops, not monolithic tools.
Wrong: deploy_and_monitor(app) — bundles judgment into code
Wrong: classify_and_organize_files(files) — agent should decide classification
Right: eve build create, eve build run, eve env deploy, eve job follow — agent decides the sequence
On Eve: The manifest defines WHAT (services, pipelines), the agent decides HOW and WHEN to compose them.
Design test: To change behavior, do you edit prose (prompts/skills) or refactor code? If code — your tools aren't atomic enough.
When tools are atomic and parity exists, you add capabilities by writing prompts, not code.
Eve example: The eve-pipelines-workflows skill adds pipeline composition capability. No new CLI commands needed — the skill teaches agents to compose existing eve pipeline and eve workflow commands.
Your app: If adding a feature requires new API endpoints, you may be bundling logic. Consider whether existing primitives can be composed differently.
Build atomic tools. Agents compose unexpected solutions. You observe patterns. Optimize common patterns. Repeat.
Eve example: Agents compose eve job create --parent + eve job dep add + depth propagation to build arbitrary work hierarchies. The platform didn't prescribe this — agents discovered it from atomic primitives.
Beyond the four principles, Eve provides (or is building) specific primitives that make agentic apps dramatically simpler:
Pass plans, reports, and insights between agents without file gymnastics. Attach text documents (markdown, JSON, YAML) to jobs. Downstream agents read attachments from parent jobs. This solves 80% of the "agents passing structured context" problem.
Use eve auth mint (today) or service accounts (emerging) to authenticate app backends. Every app with a backend needs a non-user token for API calls. Scoped permissions enforce least privilege.
Agents accumulate knowledge that outlives individual jobs: architecture reports, risk assessments, conventions. DB-backed with full-text search and agent-native search/replace editing via PATCH operations.
Choose based on your needs:
POST /internal/orgs/:id/chat/route. Full control over enrichment, storage, routing. Best for production SaaS.Decision: If your app intercepts, enriches, or stores conversations → use B. Otherwise → use A.
Portfolio views, dashboards, and any tool spanning multiple projects. Org-level endpoints eliminate N+1 API calls.
See references/eve-horizon-primitives.md for the full catalog with API schemas and priority ranking.
cat, grep, mv, mkdir.eve/manifest.yaml as single source of truth — agents read and edit itagents.yaml, teams.yaml) — not hidden in databases{entity_type}/{entity_id}/content{entity}.json, {type}.md, agent_log.mdSystem prompts should include:
Eve injects EVE_API_URL, EVE_PROJECT_ID, EVE_ORG_ID, EVE_ENV_NAME into every environment. Skills provide domain vocabulary.
json-result with eve.status ("success", "failed", "waiting")shouldContinue for multi-step operationseve job list discovers available workeve agents list discovers available agentslist_available_types()) over static tool-per-endpoint mappingthinking, toolCall, toolResult, textResponse, statusChangeephemeralToolCalls for noisy internal operationsArchitecture:
Implementation:
If building an app with a backend:
| Anti-Pattern | Fix |
|---|---|
| Agent as router only | Let agents act, not just route |
Workflow-shaped tools (analyze_and_deploy) |
Break into atomic primitives |
| UI-only actions | Maintain parity — add CLI/API paths |
| Context starvation | Inject resources via skills and env vars |
| Gates without reason | Default to open; keep primitives available |
| Heuristic completion | Use explicit completion signals |
| Static API mapping | Use dynamic capability discovery |
| Stuffing context in job descriptions | Use job attachments for structured docs |
| Per-user tokens for backends | Use service accounts / eve auth mint |
| Polling for events | Use webhooks when available (emerging) |
See references/eve-horizon-primitives.md for the full platform primitives catalog with API schemas, DB designs, and implementation priority ranking.
For the source philosophy: ../eve-horizon/docs/ideas/agent-native-design.md
For platform primitives analysis: ../eve-horizon/docs/ideas/platform-primitives-for-agentic-apps.md
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
erichowens/some_claude_skills
hyperb1iss/hyperskills
omer-metin/skills-for-antigravity
eve-agent-native-design is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
eve-agent-native-design reduced setup friction for our internal harness; good balance of opinion and flexibility.
eve-agent-native-design is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for eve-agent-native-design matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: eve-agent-native-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: eve-agent-native-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for eve-agent-native-design matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: eve-agent-native-design is focused, and the summary matches what you get after install.
Useful defaults in eve-agent-native-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: eve-agent-native-design is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 58