/knowledge-organize
Create, move, reorder, or link learning units and documents in the Knowledge base. Use when the user wants to structure content ('create unit Module 3', 'move these docs to lesson 2', 'reorder lessons by logical sequence', 'link doc X to unit Y').
$ npx -y skills add evolution-foundation/evo-nexus --skill knowledge-organize --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/knowledge-organize
Context preview
The summary Claude sees to decide when to auto-load this skill.
Create, move, reorder, or link learning units and documents in the Knowledge base. Use when the user wants to structure content ('create unit Module 3', 'move these docs to lesson 2', 'reorder lessons by logical sequence', 'link doc X to unit Y').
SKILL.md
knowledge-organize.SKILL.mdname: knowledge-organize
description: "Create, move, reorder, or link learning units and documents in the Knowledge base. Use when the user wants to structure content ('create unit Module 3', 'move these docs to lesson 2', 'reorder lessons by logical sequence', 'link doc X to unit Y')."knowledge-organize
Group: **Curation**. Units: create, move, reorder, link documents.
When to trigger
- "Create unit 'Module 3'"
- "Reorder lessons by logical sequence"
- "Move these documents to unit X"
- "Link doc Y to lesson 2"
Arguments
| Name | Type | Required | Description | |---|---|---|---| | `action` | str | yes | `create` \| `move` \| `reorder` \| `link` \| `update` | | `connection` | str | no | Defaults to first ready | | (action-specific args below) | | | |
Actions
`create`
Args: `space_id` (or `space` slug), `slug`, `title`, `sequence_idx` (optional), `description`, `prerequisites` (list uuids), `metadata` (dict).
from dashboard.backend.sdk_client import evo
unit = evo.post(
"/api/knowledge/v1/units",
{"space_id": space_id, "slug": slug, "title": title, ...},
headers={"X-Knowledge-Connection": connection},
)`move` (document → unit)
Args: `document_id`, `unit_id` (null to unlink).
evo.patch(
f"/api/knowledge/v1/documents/{document_id}",
{"unit_id": unit_id},
headers={"X-Knowledge-Connection": connection},
)`reorder` (units within space)
Args: `space_id`, `ordered_ids` (list of unit uuids in desired order).
evo.post(
"/api/knowledge/v1/units/reorder",
{"space_id": space_id, "ordered_ids": ordered_ids},
headers={"X-Knowledge-Connection": connection},
)`link` (N documents → 1 unit)
Args: `unit_id`, `document_ids` (list).
for doc_id in document_ids:
evo.patch(
f"/api/knowledge/v1/documents/{doc_id}",
{"unit_id": unit_id},
headers={"X-Knowledge-Connection": connection},
)`update` (unit metadata)
Args: `unit_id`, `title`, `description`, `sequence_idx`, `prerequisites`, `metadata`.
evo.patch(
f"/api/knowledge/v1/units/{unit_id}",
{"title": title, "description": description, ...},
headers={"X-Knowledge-Connection": connection},
)Output
Confirmation per action:
✓ Unit created: {title}
slug: {slug}
space: {space}
sequence_idx: {N}
id: {uuid}For reorder:
✓ Reordered {N} units in space {space}:
1. {title_1}
2. {title_2}
...Actionable failures
- Invalid `action` → list valid actions
- `unit_id` not found → "Unit not found. Use `knowledge-browse scope=units`."
- Duplicate `sequence_idx` → suggest reorder
- Insufficient permission → "Token lacks `write` scope"
Read more
name: knowledge-organize
description: "Create, move, reorder, or link learning units and documents in the Knowledge base. Use when the user wants to structure content ('create unit Module 3', 'move these docs to lesson 2', 'reorder lessons by logical sequence', 'link doc X to unit Y')."knowledge-organize
Group: **Curation**. Units: create, move, reorder, link documents.
When to trigger
- "Create unit 'Module 3'"
- "Reorder lessons by logical sequence"
- "Move these documents to unit X"
- "Link doc Y to lesson 2"
Arguments
| Name | Type | Required | Description | |---|---|---|---| | `action` | str | yes | `create` \| `move` \| `reorder` \| `link` \| `update` | | `connection` | str | no | Defaults to first ready | | (action-specific args below) | | | |
Actions
`create`
Args: `space_id` (or `space` slug), `slug`, `title`, `sequence_idx` (optional), `description`, `prerequisites` (list uuids), `metadata` (dict).
from dashboard.backend.sdk_client import evo
unit = evo.post(
"/api/knowledge/v1/units",
{"space_id": space_id, "slug": slug, "title": title, ...},
headers={"X-Knowledge-Connection": connection},
)`move` (document → unit)
Args: `document_id`, `unit_id` (null to unlink).
evo.patch(
f"/api/knowledge/v1/documents/{document_id}",
{"unit_id": unit_id},
headers={"X-Knowledge-Connection": connection},
)`reorder` (units within space)
Args: `space_id`, `ordered_ids` (list of unit uuids in desired order).
evo.post(
"/api/knowledge/v1/units/reorder",
{"space_id": space_id, "ordered_ids": ordered_ids},
headers={"X-Knowledge-Connection": connection},
)`link` (N documents → 1 unit)
Args: `unit_id`, `document_ids` (list).
for doc_id in document_ids:
evo.patch(
f"/api/knowledge/v1/documents/{doc_id}",
{"unit_id": unit_id},
headers={"X-Knowledge-Connection": connection},
)`update` (unit metadata)
Args: `unit_id`, `title`, `description`, `sequence_idx`, `prerequisites`, `metadata`.
evo.patch(
f"/api/knowledge/v1/units/{unit_id}",
{"title": title, "description": description, ...},
headers={"X-Knowledge-Connection": connection},
)Output
Confirmation per action:
✓ Unit created: {title}
slug: {slug}
space: {space}
sequence_idx: {N}
id: {uuid}For reorder:
✓ Reordered {N} units in space {space}:
1. {title_1}
2. {title_2}
...Actionable failures
- Invalid `action` → list valid actions
- `unit_id` not found → "Unit not found. Use `knowledge-browse scope=units`."
- Duplicate `sequence_idx` → suggest reorder
- Insufficient permission → "Token lacks `write` scope"
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

