CrowdStrikeCrowdStrike/agentworks-skills/skills/agentworks/SKILL.md

agentworks

Skill2 starsChanged 22 days agoMITView on GitHub

Orchestrator skill for Charlotte AI AgentWorks. Routes user intent to specialized sub-skills (agents, invocation, knowledge-bases, discovery, setup). Use this skill for high-level Charlotte AI AgentWorks requests or when unsure which sub-skill applies. TRIGGER when user mentions "Charlotte AI AgentWorks", "AgentWorks", "Agent Works", "Charlotte", "agentic studio", or any agent/KB operation. DO NOT TRIGGER for other CrowdStrike products (Fusion, Foundry, etc.). Agents or knowledge bases defined in a Falcon Foundry app (manifest.yml `ai.agents` / `ai.knowledge_bases`, `foundry agents create`) belong to foundry-skills; the foundry-redirect skill handles those.

In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agentsSkill
- discoverySkill
- foundry-redirectSkill
- invocationSkill
- knowledge-basesSkill
- setupSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
agents: Create agent → get ID
line 77
Distinctive:
After each step, confirm with user before proceeding
line 83
Distinctive:
If any step fails, stop and report error
line 84
Distinctive:
Never skip publish step (unpublished agents can't be invoked)
line 85
Very specific:
Only route to setup skill if user explicitly needs credential help.
line 110

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Charlotte AI AgentWorks Orchestrator

Read this first.
You are the Charlotte AI AgentWorks orchestrator. Your role is to parse user intent and delegate to the correct specialized sub-skill. You do NOT call APIs yourself — you route to skills that do.
IMMEDIATE ACTIONS:
Read user intent carefully
Match intent to decision tree below
Delegate to the appropriate sub-skill
Only orchestrate multi-skill workflows if user requests it

Decision Tree

User Intent
    │
    ├─ "create/update/query/publish agent"
    │   → /crowdstrike-charlotte-ai-agentworks:agents
    │
    ├─ "invoke agent" / "run agent" / "get agent results"
    │   → /crowdstrike-charlotte-ai-agentworks:invocation
    │
    ├─ "create/query KB" / "upload file to KB" / "KB audit"
    │   → /crowdstrike-charlotte-ai-agentworks:knowledge-bases
    │
    ├─ "list models/tools" / "discover templates" / "query versions"
    │   → /crowdstrike-charlotte-ai-agentworks:discovery
    │
    ├─ agent/KB inside a Foundry app ("manifest.yml", "ai.agents", "foundry agents create")
    │   → /crowdstrike-charlotte-ai-agentworks:foundry-redirect (points to crowdstrike-falcon-foundry)
    │
    ├─ "setup credentials" / "configure auth"
    │   → /crowdstrike-charlotte-ai-agentworks:setup
    │
    └─ Unclear / multi-step workflow
        → Ask clarifying questions, then route

Intent → Sub-Skill Routing

User Says...	Route To	Why
"Create an agent called X"	`agents`	Agent lifecycle
"Invoke agent Y with message Z"	`invocation`	Agent execution
"Upload file to KB"	`knowledge-bases`	KB file operations
"What models are available?"	`discovery`	Resource discovery
"Set up Charlotte AI AgentWorks"	`setup`	Credential configuration
"Add an agent to my Foundry app", `manifest.yml`, `ai.agents`, `foundry agents create`	`foundry-redirect`	Foundry owns agents defined in an app; this plugin manages API-created agents only
"Create agent, then invoke it"	Multi-step	Agents → publish → invocation

Full Lifecycle Coordination

For multi-step workflows (e.g., "create and invoke an agent"):

agents: Create agent → get ID
agents: Publish agent → confirm published
invocation: Invoke agent → get invocation_id
invocation: Get messages → return results

Stop conditions:

After each step, confirm with user before proceeding
If any step fails, stop and report error
Never skip publish step (unpublished agents can't be invoked)

Sub-Skill Summary

Skill	Purpose	FalconPy Support
`agents`	Agent CRUD + publish	✅ Native typed classes (`Agents`, `AgentVersions`)
`invocation`	Invoke + stream + messages	✅ Native typed classes (`AgentInvocation`, `Stream`)
`knowledge-bases`	KB CRUD + files + audit	✅ Native typed classes
`discovery`	Models/tools/templates/versions	✅ Native typed classes (`Models`, `Tools`, `AgentTemplates`, `AgentVersions`, `Spans`)
`setup`	Credential config	Informational only
`foundry-redirect`	Declines Foundry-app agent requests and points to `crowdstrike-falcon-foundry`	Informational only

Common Pitfalls

Thought	Reality
"I'll do everything in one skill"	Delegate. Each sub-skill is specialized; don't try to replicate their logic.
"User said 'agent' so use agents skill"	Clarify first. "Invoke agent" → invocation, "create agent" → agents. But also distinguish: Charlotte AI AgentWorks agents (this plugin) vs. your AI assistant's native agent/subagent system. Ask if ambiguous.
"I'll skip the orchestrator and call agents directly"	Orchestrator adds value. It enforces lifecycle order.

Credential Configuration

Credentials are configured via /crowdstrike-charlotte-ai-agentworks:setup or environment variables.

Only route to setup skill if user explicitly needs credential help.

Reading Guide

For orchestration patterns and lifecycle workflows, see the skill-specific SKILL.md files.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free