Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Operate the Neonous AI agent platform — create agents, chat, manage tools, run workflows.
.claude/skills/leoyeai-neonous/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 939% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 130% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 458% | 0% |
| case-05 | ✗→✓ | ▲ Improved | 253% | 0% |
| case-06 | ✗→✓ | ▲ Improved | 479% | 0% |
You can operate the Neonous AI agent platform on behalf of the user. Neonous lets users create, configure, and deploy AI agents through a web interface — with tools, MCP servers, workflows, templates, and more.
Prefer suggesting the web interface for complex or visual tasks:
Use the API for quick operations:
The web interface is at $NEONOUS_URL — guide the user there for anything visual or complex.
All API requests require the user's API key:
-H "x-api-key: $NEONOUS_API_KEY"Base URL: $NEONOUS_URL (e.g., https://app.neonous-ai.com).
Users generate API keys from the Settings page in Neonous. The key starts with nn_ and is only shown once. If not set up yet:
$NEONOUS_URLNEONOUS_API_KEYbashcurl -s "$NEONOUS_URL/custom/builder/agents" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.[]| {id, name, model, enabled}'
bashcurl -s "$NEONOUS_URL/custom/builder/agents/<AGENT_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Returns full config including instructions, predefined_tools, custom_tools, mcp_servers.
Always fetch models before creating an agent — do not hardcode model IDs:
bashcurl -s "$NEONOUS_URL/custom/builder/agents/available-models" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.models[]| {id, provider, display_name, is_default}'
Use the model marked is_default: true unless the user requests a specific one.
bashcurl -s "$NEONOUS_URL/custom/builder/agents/available-tools" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.tools[]| {id, name, description}'
Returns pre-defined tools that can be assigned to agents via predefined_tools.
For complex agents, recommend the web UI — it has AI-assisted generation and a template gallery. For simple agents via API:
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/agents" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "My Agent", "description": "A helpful assistant", "instructions": "You are a helpful assistant that...", "model": "<MODEL_ID from available-models>", "enabled": true, "predefined_tools": [], "custom_tools": [], "mcp_servers": [] }' | jq .
Let Neonous AI generate a full agent config from a name and description:
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/agents/generate" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "Code Reviewer", "description": "Reviews pull requests and suggests improvements" }' | jq .
Returns a complete agent config (name, instructions, model, tools) ready to use with the create endpoint.
Improve existing agent instructions with AI:
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/enhance-instructions" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"instructions": "You help with code"}' | jq '.enhanced'
bashcurl -s -X PUT "$NEONOUS_URL/custom/builder/agents/<AGENT_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "Updated Name", "instructions": "Updated instructions..." }' | jq .
Only include fields you want to change.
bashcurl -s -X DELETE "$NEONOUS_URL/custom/builder/agents/<AGENT_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Non-streaming generate endpoint — returns a complete JSON response:
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/chat/generate" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "x-agent-id: <AGENT_ID>" \ -H "Content-Type: application/json" \ -d '{"messages": [{"role": "user", "content": "Hello, what can you do?"}]}' | jq .
Response:
json{ "response": "Hi! I can help you with...", "usage": { "inputTokens": 42, "outputTokens": 18, "totalTokens": 60 } }
For multi-turn conversations, include the full message history:
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/chat/generate" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "x-agent-id: <AGENT_ID>" \ -H "Content-Type: application/json" \ -d '{ "messages": [ {"role": "user", "content": "What is 2+2?"}, {"role": "assistant", "content": "4"}, {"role": "user", "content": "Multiply that by 10"} ] }' | jq .
bashcurl -s "$NEONOUS_URL/custom/builder/chat/sessions" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.sessions[]| {id, title, agentId, created_at}'
Filter by agent: append ?agentId=<AGENT_ID>.
bashcurl -s "$NEONOUS_URL/custom/builder/chat/sessions/<SESSION_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/chat/sessions" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"agentId": "<AGENT_ID>", "title": "My Session"}' | jq .
bashcurl -s -X DELETE "$NEONOUS_URL/custom/builder/chat/sessions/<SESSION_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
For adding MCP servers, recommend the web UI — it has a searchable catalog with one-click install and secure environment variable management.
bashcurl -s "$NEONOUS_URL/custom/builder/mcp" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.[]| {id, name, type, enabled}'
bashcurl -s "$NEONOUS_URL/custom/builder/mcp/<MCP_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bashcurl -s "$NEONOUS_URL/custom/builder/mcp/<MCP_ID>/tools" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.tools[]| {name, description}'
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/mcp" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "id": "my-mcp", "name": "My MCP Server", "description": "Provides extra tools", "config": { "connectionType": "stdio", "command": "npx", "args": ["-y", "@example/mcp-server"], "envVars": [] } }' | jq .
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/mcp" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "id": "my-http-mcp", "name": "My HTTP MCP", "config": { "connectionType": "http", "url": "https://mcp.example.com/sse", "headers": {} } }' | jq .
bashcurl -s -X DELETE "$NEONOUS_URL/custom/builder/mcp/<MCP_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Add ?force=true to delete even if agents are using it.
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/mcp/<MCP_ID>/test" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
For building workflows, always recommend the web UI — it has a visual drag-and-drop canvas editor that's far easier than raw JSON.
bashcurl -s "$NEONOUS_URL/custom/builder/workflows" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.[]| {id, name, enabled}'
bashcurl -s "$NEONOUS_URL/custom/builder/workflows/<WORKFLOW_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bashcurl -s -X POST "$NEONOUS_URL/custom/builder/workflows/<WORKFLOW_ID>/execute" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"input": {"key": "value"}}' | jq .
bashcurl -s "$NEONOUS_URL/custom/builder/workflows/<WORKFLOW_ID>/runs?limit=10" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.runs[]| {id, status, created_at}'
bashcurl -s "$NEONOUS_URL/custom/builder/workflows/runs/<RUN_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bashcurl -s "$NEONOUS_URL/custom/builder/workflows/runs/<RUN_ID>/logs" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.logs'
bashcurl -s "$NEONOUS_URL/custom/builder/templates" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.templates[]| {id, name, category}'
Filter by category: append ?category=<CATEGORY>.
bashcurl -s "$NEONOUS_URL/custom/builder/templates/<TEMPLATE_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bashcurl -s "$NEONOUS_URL/custom/builder/community-templates" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.templates[]| {id, name, category, author}'
For browsing and cloning templates, recommend the web UI — it has previews, categories, and one-click clone.
bashcurl -s "$NEONOUS_URL/custom/builder/community-mcp" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.[]| {id, name, categories}'
Agents generate artifacts during chat — code files, documents, charts, diagrams, and more. These are automatically saved and versioned. Users organize artifacts into spaces (project-based collections). For full artifact management, recommend the web UI — it has a file-manager interface with drag-and-drop, folders, and visual previews.
bash# List all artifacts curl -s "$NEONOUS_URL/custom/builder/artifacts" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.[]| {id, title, type, created_at}' # Get artifact details curl -s "$NEONOUS_URL/custom/builder/artifacts/<ARTIFACT_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Search artifacts curl -s "$NEONOUS_URL/custom/builder/artifacts/search?q=<QUERY>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Quick search curl -s "$NEONOUS_URL/custom/builder/artifacts/quick-search?q=<QUERY>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Recent / Starred / Trash curl -s "$NEONOUS_URL/custom/builder/artifacts/recent" -H "x-api-key: $NEONOUS_API_KEY" | jq . curl -s "$NEONOUS_URL/custom/builder/artifacts/starred" -H "x-api-key: $NEONOUS_API_KEY" | jq . curl -s "$NEONOUS_URL/custom/builder/artifacts/trash" -H "x-api-key: $NEONOUS_API_KEY" | jq . # Stats and tags curl -s "$NEONOUS_URL/custom/builder/artifacts/stats" -H "x-api-key: $NEONOUS_API_KEY" | jq . curl -s "$NEONOUS_URL/custom/builder/artifacts/tags" -H "x-api-key: $NEONOUS_API_KEY" | jq .
bash# List versions curl -s "$NEONOUS_URL/custom/builder/artifacts/<ARTIFACT_ID>/versions" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Restore a version curl -s -X POST "$NEONOUS_URL/custom/builder/artifacts/<ARTIFACT_ID>/versions/<VERSION>/restore" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bash# Create folder curl -s -X POST "$NEONOUS_URL/custom/builder/artifacts/folders" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "My Folder"}' | jq . # Get folder contents curl -s "$NEONOUS_URL/custom/builder/artifacts/folders/<FOLDER_ID>/contents" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Move artifacts to folder curl -s -X POST "$NEONOUS_URL/custom/builder/artifacts/move" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"artifactIds": ["<ID1>", "<ID2>"], "folderId": "<FOLDER_ID>"}' | jq .
bash# Share artifact (returns a public share link) curl -s -X POST "$NEONOUS_URL/custom/builder/artifacts/<ARTIFACT_ID>/share" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Revoke share curl -s -X DELETE "$NEONOUS_URL/custom/builder/artifacts/shares/<SHARE_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bash# Delete (moves to trash) curl -s -X DELETE "$NEONOUS_URL/custom/builder/artifacts/<ARTIFACT_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Restore from trash curl -s -X POST "$NEONOUS_URL/custom/builder/artifacts/<ARTIFACT_ID>/restore" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Duplicate curl -s -X POST "$NEONOUS_URL/custom/builder/artifacts/<ARTIFACT_ID>/duplicate" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Empty trash curl -s -X DELETE "$NEONOUS_URL/custom/builder/artifacts/trash" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Spaces group artifacts by project or topic. An artifact can belong to multiple spaces.
bash# List spaces curl -s "$NEONOUS_URL/custom/builder/spaces" \ -H "x-api-key: $NEONOUS_API_KEY" | jq '.spaces[]| {id, name, description}' # Get space (with its artifacts) curl -s "$NEONOUS_URL/custom/builder/spaces/<SPACE_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Create space curl -s -X POST "$NEONOUS_URL/custom/builder/spaces" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "My Project", "description": "Artifacts for my project", "icon": "📁", "color": "#3B82F6"}' | jq . # Update space curl -s -X PUT "$NEONOUS_URL/custom/builder/spaces/<SPACE_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "Renamed Space"}' | jq . # Delete space curl -s -X DELETE "$NEONOUS_URL/custom/builder/spaces/<SPACE_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Add artifact to space curl -s -X POST "$NEONOUS_URL/custom/builder/spaces/<SPACE_ID>/artifacts" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"artifactId": "<ARTIFACT_ID>"}' | jq . # Remove artifact from space curl -s -X DELETE "$NEONOUS_URL/custom/builder/spaces/<SPACE_ID>/artifacts/<ARTIFACT_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Save important messages from chat sessions.
bash# List bookmarks curl -s "$NEONOUS_URL/custom/builder/bookmarks" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # List bookmark tags curl -s "$NEONOUS_URL/custom/builder/bookmarks/tags" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Get bookmarks for a session curl -s "$NEONOUS_URL/custom/builder/bookmarks/session/<SESSION_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Create bookmark curl -s -X POST "$NEONOUS_URL/custom/builder/bookmarks" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"sessionId": "<SESSION_ID>", "messageId": "<MSG_ID>", "tags": ["important"]}' | jq . # Delete bookmark curl -s -X DELETE "$NEONOUS_URL/custom/builder/bookmarks/<BOOKMARK_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Agent skills extend what agents can do.
bash# List skills curl -s "$NEONOUS_URL/custom/builder/skills" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Get skill details curl -s "$NEONOUS_URL/custom/builder/skills/<SKILL_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Agents can set reminders that trigger notifications or AI-generated follow-ups.
bash# List reminders curl -s "$NEONOUS_URL/custom/builder/reminders" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Create reminder (schedule is a cron expression) curl -s -X POST "$NEONOUS_URL/custom/builder/reminders" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "title": "Check deployment", "message": "Verify the production deploy succeeded", "agentId": "<AGENT_ID>", "schedule": "0 9 * * *" }' | jq . # Toggle reminder on/off curl -s -X POST "$NEONOUS_URL/custom/builder/reminders/<REMINDER_ID>/toggle" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Delete reminder curl -s -X DELETE "$NEONOUS_URL/custom/builder/reminders/<REMINDER_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # List notifications curl -s "$NEONOUS_URL/custom/builder/notifications" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Unread count curl -s "$NEONOUS_URL/custom/builder/notifications/unread-count" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Mark all notifications read curl -s -X POST "$NEONOUS_URL/custom/builder/notifications/read-all" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Connect agents to Telegram bots. For setup, recommend the web UI — it handles bot token configuration.
bash# List Telegram connections curl -s "$NEONOUS_URL/custom/builder/telegram/connections" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Connect agent to Telegram curl -s -X POST "$NEONOUS_URL/custom/builder/telegram/connect" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"agentId": "<AGENT_ID>", "botToken": "<TELEGRAM_BOT_TOKEN>"}' | jq . # Disconnect curl -s -X DELETE "$NEONOUS_URL/custom/builder/telegram/connections/<CONNECTION_ID>" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Agents remember context across conversations via working memory.
bash# Get working memory curl -s "$NEONOUS_URL/custom/builder/users/working-memory" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Reset working memory curl -s -X DELETE "$NEONOUS_URL/custom/builder/users/working-memory" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Users can submit and vote on feature wishes.
bash# List wishes curl -s "$NEONOUS_URL/custom/builder/wishes" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Create wish curl -s -X POST "$NEONOUS_URL/custom/builder/wishes" \ -H "x-api-key: $NEONOUS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"title": "Feature request", "description": "I would like..."}' | jq . # Upvote/un-upvote curl -s -X POST "$NEONOUS_URL/custom/builder/wishes/<WISH_ID>/upvote" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bashcurl -s "$NEONOUS_URL/tokens/balance" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bashcurl -s "$NEONOUS_URL/tokens/usage" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
bashcurl -s "$NEONOUS_URL/tokens/summary" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
Subscribing, upgrading plans, and purchasing tokens all go through Stripe checkout in the browser. Always direct users to the web UI at $NEONOUS_URL/settings (or the billing/pricing page) to subscribe or buy tokens — these cannot be completed via API alone.
You can check the user's current plan and billing status via API:
bash# Get available plans (shows what they can subscribe to) curl -s "$NEONOUS_URL/custom/builder/billing/plans" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Get current subscription (shows active plan) curl -s "$NEONOUS_URL/custom/builder/billing/subscription" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Get billing status curl -s "$NEONOUS_URL/custom/builder/billing/status" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Get token pricing (for purchasing extra tokens) curl -s "$NEONOUS_URL/custom/builder/billing/token-pricing" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Get purchase history curl -s "$NEONOUS_URL/custom/builder/billing/purchases" \ -H "x-api-key: $NEONOUS_API_KEY" | jq . # Get invoices curl -s "$NEONOUS_URL/custom/builder/billing/invoices" \ -H "x-api-key: $NEONOUS_API_KEY" | jq .
If the user wants to subscribe, upgrade, or buy tokens, tell them to visit the Settings > Billing page in the web UI.
bashcurl -s "$NEONOUS_URL/custom/builder/health" | jq .
No authentication required.
available-models endpoint.| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 5,591 | 11,796 | +111% | 1 | 1 | 0% | 873 | 9,071 | +939% | 0 | 0 | — |
case-02 | fail→pass | 17,757 | 6,917 | -61% | 1 | 1 | 0% | 3,781 | 8,713 | +130% | 0 | 0 | — |
case-03 | fail→fail | 5,864 | 6,940 | +18% | 1 | 1 | 0% | 941 | 7,805 | +729% | 0 | 0 | — |
case-04 | fail→pass | 7,761 | 5,575 | -28% | 1 | 1 | 0% | 1,515 | 8,457 | +458% | 0 | 0 | — |
case-05 | fail→pass | 12,142 | 3,117 | -74% | 1 | 1 | 0% | 2,249 | 7,940 | +253% | 0 | 0 | — |
case-06 | fail→pass | 7,126 | 3,034 | -57% | 1 | 1 | 0% | 1,377 | 7,968 | +479% | 0 | 0 | — |
case-07 | fail→pass | 13,283 | 3,392 | -74% | 1 | 1 | 0% | 2,190 | 7,983 | +265% | 0 | 0 | — |
case-08 | fail→pass | 9,127 | 3,665 | -60% | 1 | 1 | 0% | 1,543 | 8,110 | +426% | 0 | 0 | — |
case-18 | fail→pass | 13,913 | 2,920 | -79% | 1 | 1 | 0% | 2,213 | 7,838 | +254% | 0 | 0 | — |
case-09 | fail→pass | 8,669 | 3,796 | -56% | 1 | 1 | 0% | 1,706 | 8,114 | +376% | 0 | 0 | — |
case-10 | fail→pass | 5,870 | 1,932 | -67% | 1 | 1 | 0% | 930 | 7,744 | +733% | 0 | 0 | — |
case-11 | fail→pass | 10,101 | 3,067 | -70% | 1 | 1 | 0% | 2,022 | 7,976 | +294% | 0 | 0 | — |
case-12 | fail→pass | 11,622 | 2,450 | -79% | 1 | 1 | 0% | 2,180 | 7,869 | +261% | 0 | 0 | — |
case-13 | fail→pass | 6,112 | 2,939 | -52% | 1 | 1 | 0% | 389 | 7,967 | +1948% | 0 | 0 | — |
case-14 | fail→pass | 6,714 | 4,130 | -38% | 1 | 1 | 0% | 1,273 | 8,188 | +543% | 0 | 0 | — |
case-15 | fail→pass | 6,409 | 3,503 | -45% | 1 | 1 | 0% | 1,271 | 8,059 | +534% | 0 | 0 | — |
case-16 | fail→pass | 7,259 | 2,103 | -71% | 1 | 1 | 0% | 1,291 | 7,738 | +499% | 0 | 0 | — |
case-17 | fail→pass | 7,697 | 3,599 | -53% | 1 | 1 | 0% | 673 | 7,983 | +1086% | 0 | 0 | — |
case-19 | fail→pass | 4,622 | 5,442 | +18% | 1 | 1 | 0% | 712 | 7,869 | +1005% | 0 | 0 | — |
case-20 | pass→pass | 2,570 | 3,301 | +28% | 1 | 1 | 0% | 433 | 7,978 | +1742% | 0 | 0 | — |
case-21 | pass→pass | 4,224 | 3,766 | -11% | 1 | 1 | 0% | 706 | 8,029 | +1037% | 0 | 0 | — |
case-22 | pass→pass | 3,809 | 3,103 | -19% | 1 | 1 | 0% | 627 | 7,788 | +1142% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 20 counted toward the lift figure. The other 2 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +82 percentage points is the difference between those two pass rates over the 20 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.