agentleFS
OpenBMBOpenBMB/EC2-Bench/skills/clawbenchz_vault_1/SKILL.md

clawbenchz_vault_1

Skill19 starsChanged 5 months agoMITView on GitHub

Base URL: http://localhost:9130 Returns available vault categories and their field requirements. Response 200: Create a new vault item. Request body (JSON): Response 201: Error 400: unknown category. Error 422: missing required fields. List all vault items (summary only — no secret fields). Response 200: Full audit log (for automated grading only — do not call during migration).

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a new vault item.

    line 43

≈ “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

Password Vault API

Base URL: http://localhost:9130

Endpoints

GET /vault/schema

Returns available vault categories and their field requirements.

Response 200:

{
  "categories": {
    "login": {
      "description": "Website or app login credentials",
      "required_fields": ["title", "username", "password"],
      "optional_fields": ["url", "totp_secret", "mfa_enabled", "notes", "tags", "priority", "last_rotated"]
    },
    "credit_card": {
      "description": "Credit or debit card",
      "required_fields": ["title", "cardholder", "card_number", "expiry", "cvv"],
      "optional_fields": ["pin", "bank", "notes", "tags", "priority", "last_rotated"]
    },
    "secure_note": {
      "description": "Encrypted free-form text for sensitive info",
      "required_fields": ["title", "content"],
      "optional_fields": ["notes", "tags", "priority", "last_rotated"]
    },
    "api_credential": {
      "description": "API keys, tokens, or service-account secrets",
      "required_fields": ["title", "credential_value"],
      "optional_fields": ["service_name", "environment", "notes", "tags", "priority", "last_rotated"]
    }
  },
  "policy_notes": "..."
}

POST /vault/items

Create a new vault item.

Request body (JSON):

{
  "category": "login",
  "fields": {
    "title": "GitHub Personal",
    "username": "alexgreen-dev",
    "password": "...",
    "url": "https://github.com",
    "tags": ["development"],
    "mfa_enabled": true,
    "totp_secret": "..."
  }
}

Response 201:

{
  "status": "created",
  "item_id": "vault_001",
  "category": "login"
}

Error 400: unknown category. Error 422: missing required fields.

GET /vault/items

List all vault items (summary only — no secret fields).

Response 200:

{
  "items": [
    {"id": "vault_001", "category": "login", "title": "GitHub Personal", "created_at": "..."}
  ],
  "total": 1
}

GET /vault/audit

Full audit log (for automated grading only — do not call during migration).

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.