agentleFS
Sign inStart free
Google CloudKnown publisherGoogleCloudPlatform/devrel-demos/agents/charm-persona-quiz-for-agents/llms.txt

devrel-demos / charm-persona-quiz-for-agents

llms.txt404 starsChanged 13 days agoApache-2.0View on GitHub

1. Fetch the 15 scenario prompts: GET /api/questions 2. Submit your multi-sentence paragraph answers (2-5 sentences each, >= 8 words & >= 40 chars) for q1 through q15: POST /api/submit Content-Type: application/json { "agent_id": "your-agent-name", "agent_model": "your-model-id", "agent_harness": "your-harness-or-framework", "answers": { "q1": "...", "q2": "...", "...": "...", "q15": "..." } } POST /api/submit validates your answers and stages them live on any open CHARM UI tab. When done, ask a human to click the 'Score Your Persona!' button in the…

The file

We split this llms.txt into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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
  1. Very specific:

    Use window.CHARM_AGENT_API.getQuestions(), window.CHARM_AGENT_API.fillResponses({ q1, ..., q15 }, agentId, agentModel, agentHarness), and …

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt 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
llms.txt
# CHARM — Agent Operational Scenario Assessment (charm.v1)

## Fastest Way to Take This Test (2 HTTP Calls, No Browser Needed)

1. Fetch the 15 scenario prompts:
   GET /api/questions

2. Submit your multi-sentence paragraph answers (2-5 sentences each, >= 8 words & >= 40 chars) for q1 through q15:
   POST /api/submit
   Content-Type: application/json

   {
     "agent_id": "your-agent-name",
     "agent_model": "your-model-id",
     "agent_harness": "your-harness-or-framework",
     "answers": {
       "q1": "...",
       "q2": "...",
       "...": "...",
       "q15": "..."
     }
   }

`POST /api/submit` validates your answers and stages them live on any open CHARM UI tab. When done, ask a human to click the `'Score Your Persona!'` button in the app to reveal your traits!

## Browser Alternative (if already in a browser session)
Use `window.CHARM_AGENT_API.getQuestions()`, `window.CHARM_AGENT_API.fillResponses({ q1, ..., q15 }, agentId, agentModel, agentHarness)`, and `window.CHARM_AGENT_API.evaluate()`.

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