agentworks-skills
AGENTS.md2 starsChanged 22 days agoMITView on GitHub
A tool-agnostic guide to the agentworks-skills plugin for AI coding assistants that are not Claude Code (Codex, GitHub Copilot, Cursor, Antigravity, and others). Claude Code users get the same content via the plugin system and CLAUDE.md; this file lets any agent use the skills directly. agentworks-skills lets an assistant create, configure, invoke, and analyze Charlotte AI AgentWorks agents through the Falcon API, manage their knowledge bases, and discover the models, tools, templates, and trace spans available to them. Agents created…
- Installs packages
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agentsSkill
- agentworksSkill
- discoverySkill
- foundry-redirectSkill
- invocationSkill
- knowledge-basesSkill
- setupSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 76
Never guess agent, version, knowledge base, file, or invocation IDs — query first (agent_search.py, kb_search.py, …).
- Distinctive: line 79
Delete operations and agent enable/disable are out of scope for v1.
- Very specific: line 80
Look at real traces (analyze_agent.py, inspect_invocation.py) before suggesting prompt changes.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.
Files
AGENTS.md
A tool-agnostic guide to the agentworks-skills plugin for AI coding assistants that are not Claude Code (Codex, GitHub Copilot, Cursor, Antigravity, and others). Claude Code users get the same content via the plugin system and CLAUDE.md; this file lets any agent use the skills directly.
What This Is
agentworks-skills lets an assistant create, configure, invoke, and analyze Charlotte AI AgentWorks agents through the Falcon API, manage their knowledge bases, and discover the models, tools, templates, and trace spans available to them.
Agents created and managed directly through the API belong to this plugin. Agents defined inside a Falcon Foundry app's manifest.yml (ai.agents) are part of that app — use the foundry-skills plugin for those.
Prerequisites
- Python 3.14+
- crowdstrike-falconpy 1.6.6+ (
pip install crowdstrike-falconpy) - Falcon API OAuth 2.0 client credentials with the
charlotte-ai-agent-definition:readandcharlotte-ai-agent-definition:writescopes
Configure credentials with the setup command (writes the TOML profile at ~/.cache/crowdstrike-charlotte-ai-agentworks/credentials.toml):
/crowdstrike-charlotte-ai-agentworks:setupFor CI or a one-off override, set environment variables instead:
export FALCON_CLIENT_ID=your_client_id_here
export FALCON_CLIENT_SECRET=your_client_secret_here
# export FALCON_BASE_URL=https://api.crowdstrike.com # US-1 (default)Verify credentials:
python common/scripts/auth.pyRepository Structure
skills/
agentworks/ Orchestrator skill — SKILL.md decision tree, routes to the skills below
agents/ agent_upsert/get/list/search/publish, analyze_agent, compare_versions
invocation/ invoke_agent/version, get_messages, stream_invocation, cancel_invocation, list_invocations, inspect_invocation
knowledge-bases/ kb_upsert/get/list/search, kb_files_list, kb_file_upload/download, kb_audit
discovery/ models/tools/templates/versions/spans search and get
setup/ SKILL.md — interactive credential setup
foundry-redirect/ SKILL.md — points Foundry-app agent requests to foundry-skills
common/scripts/ auth.py (shared API auth), discovery_helpers.py, invocation_helpers.py, formatting.py, waterfall.py, _bootstrap.py
hooks/ Plugin hooks (venv bootstrap, intent routing)
release.sh Version bump and Codex bundle builder (see docs/RELEASING.md)
references/ Cross-skill reference docsEach skill's SKILL.md is plain markdown with YAML frontmatter — read it directly for the workflow, script reference, and pitfalls. Reference docs live under each skill's references/ directory.
Skills Ecosystem
| Skill | Use it to |
agentworks | Understand routing between the skills (read this first) |
agents | Create, update, query, publish, and analyze agents |
invocation | Invoke agents (published or a specific version), read messages, cancel, inspect traces |
knowledge-bases | Manage knowledge bases, their files, and audit events |
discovery | Find models, tools, templates, agent versions, and trace spans |
setup | Configure credentials |
foundry-redirect | Decline agent/KB requests for a Foundry app and point to foundry-skills |
Using Without the Claude Code Plugin System
The skills are markdown instructions plus Python scripts — no plugin runtime is required.
- Read the SKILL.md for the task you are doing (e.g.,
skills/agents/SKILL.mdto create an agent). - Run the scripts from the skill's folder through the managed-venv wrapper:
cd skills/<skill> && ../../scripts/python.sh scripts/<script>.py --help.${CLAUDE_PLUGIN_ROOT}(set only by Claude Code) is not required. A script started with a barepythonthat lacks FalconPy re-executes itself through the wrapper, which builds the venv on first use. - Follow the discipline rules, which are not optional:
- Never guess agent, version, knowledge base, file, or invocation IDs — query first (
agent_search.py,kb_search.py, …). - Tool IDs come from
tools_get.py/tools_search.py, and model IDs frommodels_search.py; they are opaque strings, not UUIDs. - A draft version cannot be invoked with
invoke_agent.py; useinvoke_version.pywith the version ID. Publish withagent_publish.pybefore usinginvoke_agent.py. - Delete operations and agent enable/disable are out of scope for v1.
- Look at real traces (
analyze_agent.py,inspect_invocation.py) before suggesting prompt changes.
- Never guess agent, version, knowledge base, file, or invocation IDs — query first (
Lifecycle at a Glance
discover models/tools → upsert agent → invoke a version → inspect / analyze → refine → publish
(discovery) (agents) (invocation) (invocation, agents) (agents) (agents)Carry the artifacts forward: agent_upsert.py returns an agent ID and a version ID, invocation returns an invocation ID, and inspect_invocation.py resolves the trace from that invocation ID.
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.

