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

setup

Skill2 starsChanged 22 days agoMITView on GitHub

Configure credentials for Charlotte AI AgentWorks API access. Guides users through manual TOML configuration or environment variable setup. TRIGGER when user explicitly asks to "set up Charlotte AI AgentWorks", "configure credentials", or has auth errors. DO NOT TRIGGER for general Charlotte AI AgentWorks usage (orchestrator handles routing).

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord and 10 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.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 9

    Distinctive

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Should authenticate 5 FalconPy clients (KnowledgeBases, KnowledgeBaseFiles, KnowledgeBaseAuditEvents, Agents, AgentInvocation), all sharing …

    line 29
  2. Distinctive:

    Check TOML file exists and has correct profile

    line 90
  3. Distinctive:

    Verify client_id/secret are correct

    line 94
  4. Distinctive:

    Check base_url matches your Falcon cloud (us-1, us-2, eu-1, etc.)

    line 95
  5. Distinctive:

    Ensure API client has required scopes

    line 96
  6. Distinctive:

    Check network connectivity to Falcon API

    line 99
  7. Distinctive:

    Verify client_id/secret haven't been rotated

    line 100
  8. Very specific:

    Run python common/scripts/auth.py -- as of this version it prints the real API error (e.g.

    line 101
  9. Very specific:

    Check whether your organization requires a custom CA bundle for outbound HTTPS, and that Python's trust store (or …

    line 108
  10. Distinctive:

    After configuration, restart the coding agent terminal so it receives the updated environment.

    line 120
  11. Distinctive:

    Never commit credentials to git

    line 129

“Common” is measured: kept by at least 6 in 10 of the 171 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.

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

Charlotte AI AgentWorks Setup

Configuration

This plugin requires Falcon API OAuth 2.0 credentials. Configure using one of the methods below.

Test authentication:

scripts/python.sh common/scripts/auth.py

Should authenticate 5 FalconPy clients (KnowledgeBases, KnowledgeBaseFiles, KnowledgeBaseAuditEvents, Agents, AgentInvocation), all sharing one token.

Setup Methods

Option 1: TOML Profile (Recommended)

Create ~/.cache/crowdstrike-charlotte-ai-agentworks/credentials.toml:

default = "us-1"

[us-1]
client_id = "your-client-id-here"
client_secret = "your-client-secret-here"
base_url = "https://api.crowdstrike.com"  # or your cloud URL

Set permissions:

mkdir -p ~/.cache/crowdstrike-charlotte-ai-agentworks
chmod 700 ~/.cache/crowdstrike-charlotte-ai-agentworks
chmod 600 ~/.cache/crowdstrike-charlotte-ai-agentworks/credentials.toml

Option 2: Environment Variables

export FALCON_CLIENT_ID=<your-id>
export FALCON_CLIENT_SECRET=<your-secret>
export FALCON_BASE_URL=https://api.crowdstrike.com  # optional, defaults to US-1

Required API CSRN Permissions

Charlotte AI AgentWorks uses these CSRN permissions:

  • csrn:charlotte-ai:agent:definition (read + write)
  • csrn:charlotte-ai:agent:invocation (assert/execute)
  • csrn:charlotte-ai:agent:knowledge-base (read + write)
  • csrn:charlotte-ai:agent:template (read)
  • csrn:charlotte-ai:agent:metrics (read)

Verification

After setup, run:

cd /path/to/agentworks-skills
scripts/python.sh common/scripts/auth.py

Should see:

✓ Authentication successful (KnowledgeBases client)
✓ Authentication successful (KnowledgeBaseFiles client)
✓ Authentication successful (KnowledgeBaseAuditEvents client)
✓ Authentication successful (Agents client)
✓ Authentication successful (AgentInvocation client)

Troubleshooting

"No credentials found"

  • Check TOML file exists and has correct profile
  • OR set env vars

"Authentication FAILED"

  • Verify client_id/secret are correct
  • Check base_url matches your Falcon cloud (us-1, us-2, eu-1, etc.)
  • Ensure API client has required scopes

"token_expired() returns True"

  • Check network connectivity to Falcon API
  • Verify client_id/secret haven't been rotated
  • Run python common/scripts/auth.py -- as of this version it prints the real API error (e.g. bad credentials, missing scope) instead of just "could not obtain token"

Authentication fails with a certificate/TLS error during login (e.g. CERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate) -- distinct from the package-install certificate errors below; this happens on the live API call itself, often behind a TLS-intercepting proxy (e.g. Zscaler) common in corporate environments.

  • Check whether your organization requires a custom CA bundle for outbound HTTPS, and that Python's trust store (or SSL_CERT_FILE/REQUESTS_CA_BUNDLE) points at it
  • Confirm a plain curl to your base_url succeeds from the same shell/environment first -- if that also fails, this is a network/proxy config issue outside the plugin, not an Charlotte AI AgentWorks credential problem
  • These settings must be configured outside the AI coding agent; restart the coding agent terminal after configuring so it receives the updated environment

Package installation reports access, certificate, or registry errors

  • Refer the user to their organization's documentation for setting up a Python environment.
  • Their organization may require an approved package registry or specific certificates.
  • These settings must be configured outside the AI coding agent.
  • After configuration, restart the coding agent terminal so it receives the updated environment.
  • Some workstation changes may require signing out and back in before restarting the agent.

Security

  • Never paste credentials into chat
  • Credentials go only into the TOML file (via your editor) or env vars
  • TOML file should be chmod 600
  • TOML directory should be chmod 700
  • Never commit credentials to git

Multi-Cloud Support

Charlotte AI AgentWorks supports all Falcon clouds. base_url may be any Falcon cloud URL, including custom/internal environments; it is not restricted to this list:

  • US-1: https://api.crowdstrike.com (default)
  • US-2: https://api.us-2.crowdstrike.com
  • EU-1: https://api.eu-1.crowdstrike.com
  • US-GOV-1: https://api.laggar.gcw.crowdstrike.com

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.