Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →evolution-foundation/initial-setup
Welcome and onboard new EvoNexus users — introduce agents, skills, routines, and the dashboard.
Passed 12 of 17 test cases with the skill, and 8 of 17 without it.
and 6 more in the full report
8 fixed8 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
When setup creates a working folder 'workspace/finance/' with a subfolder 'workspace/finance/invoices/', should a .gitkeep file be created in both the top folder and every nested subfolder?
| Checked | Without skill | With skill |
|---|---|---|
| Places .gitkeep in the top-level folder of the workspace directory. | Missed | Passed |
| Omits creating .gitkeep inside subfolders. | Missed | Passed |
The instructions your model reads when the skill loads.
The user already has EvoNexus installed and running. Your job is to welcome them, show what's available, and help them start using agents, skills, and routines right away.
Before welcoming, ensure the workspace/ folder tree exists. The workspace is gitignored (personal data) so new installations start empty — you need to discover which agents are installed and create folders based on what each agent declares in its own system prompt, not a hardcoded list. This keeps the skill self-updating: when new agents are added (business, engineering, or custom), their folders are created automatically the next time this runs.
Read config/workspace.yaml to get workspace.owner, workspace.company, workspace.language, workspace.timezone, workspace.name. These values drive language and personalization.
List all installed agents with Glob .claude/agents/*.md. This captures:
clawdia-assistant.md, flux-finance.md, etc.)apex-architect.md, bolt-executor.md, etc.) as they get importedcustom-*.md) the user createdFor each agent file, Read it and extract:
name: ...)color: ...) — used for future dashboard integrationdescription: frontmatter field or the first prose paragraph## Working Folder section and parse the first sentence for workspace/{folder}/. If the agent has no ## Working Folder section (e.g., pure orchestrators like Clawdia, knowledge agents like Oracle), record it as "no dedicated folder" and skip folder creation for that agent.strategy/analyses/, project/github-reviews/), extract them too.## Anti-patterns, ## Absolute Rules, ## Your Level, ### REQUIRES user approval to extract the 1-2 most important conventions.Build an in-memory table of {agent, folder, subfolders, domain, conventions}. This is the source of truth for Step 1.
Check if the structure already exists. Run a quick check: if every folder in the discovered table already exists on disk, structure is already bootstrapped — skip creation and proceed to the "Customizations" summary below. Otherwise, continue.
Create folders. For each entry in the table that declares a Working Folder:
workspace/{folder}/ if missing.gitkeep in the top-level folder (subfolders don't need it — the wildcard in .gitignore handles them)Create the shared read-only folder workspace/projects/ (plural) if missing — this is where the user uploads git repositories that every agent can read. Also add a .gitkeep.
Create operational folders that are not owned by any single agent but are referenced by routines:
test cases passed, vs 8 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.