agentleFS
Sign inStart free
Sandeep-BASandeep-BA/cassandra-mcp/skills/cassandra-readonly-setup/SKILL.md

cassandra-readonly-setup

Skill0 starsChanged 15 days agoMITView on GitHub

Configure and troubleshoot the Node, Python, or Java Cassandra MCP implementations in this repository with bounded read-only access.

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the repository README and the selected implementation README.

    line 12
  2. Distinctive:

    When diagnosis fails, record runtime version, sanitized settings, expected result and error category.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Configure Cassandra MCP

Author: Sandeep Belgavi

Read the repository README and the selected implementation README. All implementations expose list_tables, describe_table, and read_partition over stdio; they are not HTTP services. Node requires Node 22+, Python uses its isolated environment, and Java runs the built executable JAR.

Use the requested runtime; do not silently install a different language. Configure exact lowercase CASSANDRA_TABLES entries and a dedicated database role with only necessary SELECT permissions. TLS verification is required outside loopback. Keep credentials outside shared files, commands, logs and screenshots. A table allowlist permits reading its rows across tenants; it is not per-user authorization.

Verify discovery first with no database read, then schema discovery and a one-row read from an authorized non-sensitive fixture. A passing protocol test does not establish live database compatibility. Use all partition-key fields and explicit columns. Large rows may consume memory before the output cap is applied.

When diagnosis fails, record runtime version, sanitized settings, expected result and error category. Do not weaken TLS, add wildcard permissions or substitute a superuser to make a test pass. Make at most one retry after a concrete correction; otherwise report the missing prerequisite.

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