create-agent
Skill6 starsChanged 8 days agoApache-2.0View on GitHub
MUST be used whenever scaffolding a new Atlas agent project. Creates agent.yaml, README.md, and a starter eval/cases.yaml with the correct structure, tool definitions, and instructions. Do NOT manually write agent.yaml from scratch — this skill handles the full scaffold. Triggers: create agent, new agent, scaffold agent, agent project, agent template, cognite agents create.
38 other projects use a version of this.
Adopted by
Most recently taken up by
- lalulali/vespyrtheir own version, first seen Nov 6, 2026
- harness/harness-skillstheir own version, first seen Nov 1, 2026
- fxmartin/claude-code-configtheir own version, first seen Oct 31, 2026
- agno-agi/agentos-dockertheir own version, first seen Oct 30, 2026
- agno-agi/agentos-flytheir own version, first seen Oct 30, 2026
- agno-agi/agentos-rendertheir own version, first seen Oct 30, 2026
Used with
Projects with it also use deploy-platform, setup-platform and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
agno-agiSkilldeploy-platform
Deploy this AgentOS using its own provider instructions, configure JWT verification, and verify the public service. Use for first deployment, redeployment, or production configuration changes.
Also in 5 projects that use this
agno-agiSkillsetup-platform
Set up this AgentOS from a fresh clone — confirm Docker, configure .env, boot the containers, prove the MCP endpoint live, connect the AgentOS UI, then build the user's first agent. Use when the user asks to set up the platform, get started, or bring this repo up on a new machine.
Also in 5 projects that use this
ElasticSkillcreate-integration
Use when creating a new Elastic integration package, scaffolding data streams, answering package layout or structure questions, or running the end-to-end integration build workflow. Covers package topology, scaffold commands, post-scaffold edits, and full orchestration of CEL/pipeline/test subagents.
Also in 3 projects that use this
MicrosoftSkillcreate-hook
Create a hook (.json) to enforce policy or automate agent lifecycle events.
Also in 5 projects that use this
AnasX7Skillimprove
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Also in 5 projects that use this
ElasticSkillcreate-skill
Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.
Also in 13 projects that use this
- +3 more from agno-agi
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- microsoft/vscode★ 195ksame name
- gnekt/My-Brain-Is-Full-Crew★ 3.9ksame name
- EvolutionAPI/evo-nexus★ 545same name
- evolution-foundation/evo-nexus★ 535same name
- openma-ai/open-managed-agents★ 348same name
- luanmorenommaciel/agentspec★ 256same name
- harness/harness-skills★ 127same name
- microsoft/copilot-studio-plugin★ 82same name
- Azure-Samples/art-voice-agent-accelerator★ 74same name
- TOKTOKHAN-DEV/agent-company★ 74same name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- aura-reviewSkill
- call-cognite-functionSkill
- code-qualitySkill
- connect-atlas-mcpSkill
- correctness-and-error-handlingSkill
- create-client-toolSkill
- dependencies-auditSkill
- designSkill
- dm-graph-traversalSkill
- dm-limits-and-best-practicesSkill
- flows-app-briefSkill
- flows-code-reviewSkill
- flows-design-reviewSkill
- flows-external-app-submitSkill
- flows-review-checksSkill
- graph-viewerSkill
- handle-startup-stateSkill
- hide-show-shellSkill
- integrate-atlas-chatSkill
- integrate-file-viewerSkill
- integrate-fusion-agentSkill
- integrate-todo-listSkill
- migrate-app-to-flowsSkill
- performanceSkill
- pull-changes-resolve-conflictsSkill
- reveal-3dSkill
- securitySkill
- setup-flows-authSkill
- setup-python-toolsSkill
- skill-creatorSkill
- start-flows-appSkill
- test-coverageSkill
- tygenSkill
- use-topbarSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Default instructions when the user doesn't specify:
- Distinctive: line 49
Run the command, including only flags where the user provided a value or a non-empty default applies:
- Very specific: line 62
Always pass --instructions (use the default if the user didn't specify).
- Very specific: line 63
Always pass --no-prompt to skip the CLI's interactive prompts.
- Very specific: line 70
If the user wants tools, edit <agent-name>/agent.yaml to add a tools array.
- Very specific: line 125
Do NOT: add tools: [] — omit the key entirely when there are no tools
- Distinctive: line 128
If a directory with the agent name already exists, warn the user and stop
“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create Agent
Scaffold a new Atlas agent project named $ARGUMENTS using npx @cognite/cli@latest agents create.
What gets created
<agent-name>/
agent.yaml # Agent definition — externalId, model, instructions, tools
README.md # Quick-start docs and tool reference
eval/
cases.yaml # Starter eval cases (single-turn, multi-turn, correctness + faithfulness scorers)Step 1 — Gather optional fields
The agent name is $ARGUMENTS. Ask the user for the following (skip any they already provided):
| Field | CLI flag | Default |
| Display name | --display-name | same as agent name |
| Description | --description | — |
| Model | --model | azure/gpt-5.4-mini |
| Instructions (system prompt) | --instructions | see default below |
| Tools | (edit after creation) | none |
Default instructions when the user doesn't specify:
Help users explore and understand the data in this project.
Use the available tools to retrieve data before answering.
When the data is insufficient, say so rather than guessing.Step 2 — Run npx @cognite/cli@latest agents create
Run the command, including only flags where the user provided a value or a non-empty default applies:
npx @cognite/cli@latest agents create <agent-name> \
--display-name "<display-name>" \
--description "<description>" \
--model <model> \
--instructions "<instructions>" \
--no-prompt- Omit
--display-nameif the user wants the default (same as agent name). - Omit
--descriptionif none was given. - Always pass
--instructions(use the default if the user didn't specify). - Always pass
--no-promptto skip the CLI's interactive prompts. - For multi-line instructions, pass them as-is in quotes; if the shell quoting is awkward, skip
--instructionsand editagent.yamlmanually after creation.
Step 3 — Add tools (if any)
If the user wants tools, edit <agent-name>/agent.yaml to add a tools array. Do NOT add tools: [] — omit the key entirely when there are no tools.
Available tool types
| Type | Purpose |
analyzeData | Analyze tabular or structured data |
analyzeImage | Analyze images and P&ID diagrams |
analyzeTimeSeries | Analyze time series data |
askDocument | Ask questions about documents |
callFunction | Call a Cognite Function |
callRestApi | Call an external REST API |
callWebhook | POST a payload to an external webhook |
examineDataSemantically | Semantic data examination |
query | Structured queries against CDF data models |
queryKnowledgeGraph | Query CDF data models with natural language |
queryTimeSeriesDatapoints | Fetch raw or aggregated time series data |
runPythonCode | Execute custom Python code |
summarizeDocument | Summarize documents |
timeSeriesAnalysis | Advanced time series analysis and anomaly detection |
Example — knowledge graph tool
tools:
- name: find_assets
type: queryKnowledgeGraph
description: Find assets and related instances in the knowledge graph.
configuration:
version: v2
dataModels:
- space: cdf_cdm
externalId: CogniteCore
version: v1
viewExternalIds:
- CogniteAsset
instanceSpaces:
type: allStep 4 — Verify and summarize
- Confirm
agent.yaml,README.md, andeval/cases.yamlwere all created - Tell the user the next steps:
- Edit
<agent-name>/agent.yaml— add tools and refine instructions npx @cognite/cli@latest agents push <externalId>— push to CDF for testingnpx @cognite/cli@latest agents open— open in Fusion- Edit
<agent-name>/eval/cases.yamland runnpx @cognite/cli@latest agents eval <externalId>— the scaffolded cases are placeholders (acorrectnesscase, afaithfulnesscase, and a multi-turn case); update the inputs, references, and context to match what the agent actually does
- Edit
Guard rails
- Do NOT add
tools: []— omit the key entirely when there are no tools - Do NOT invent tool types not listed above
- Agent name must be kebab-case: lowercase letters, digits, and hyphens only
- If a directory with the agent name already exists, warn the user and stop
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

