agentleFS
Sign inStart free
KellisLabKellisLab/mantis-cli/skills/createmap/SKILL.md

createmap

Skill2 starsChanged 5 months agoMITView on GitHub

Create a Mantis map from a local CSV or XLSX file using the mantis CLI. Run `mantis use get_space_context` first when Mantis is mentioned.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. anibajpai2/mantis-cli★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Use the local mantis create map CLI.

    line 12
  2. Distinctive:

    Ask where to put the map if the user did not specify:

    line 35
  3. Very specific:

    Run mantis create map with explicit flags.

    line 39
  4. Very specific:

    If the user wants a fully interactive human flow, run only mantis create map "./dataset.csv".

    line 70
  5. Distinctive:

    If an agent is driving the flow, avoid interactive prompts by passing flags.

    line 71
  6. Very specific:

    Use mantis setup first if the CLI says API key or URL is missing.

    line 72

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

Create Mantis Map

First: mantis use get_space_context (unless you just ran it this turn).

Use the local mantis create map CLI. Prefer passing arguments explicitly so this works for agents and humans.

Steps

  1. Get the local CSV/XLSX path from $ARGUMENTS or ask the user for it.

  2. Inspect the header row if it is a CSV. Decide field types (each has a matching --<type>-column flag, comma-separated):

    • title: one human-readable identifier column, usually title, name, path, or file.
    • semantic: text columns to embed, usually content, summary, description, text, or body.
    • categoric: labels like language, kind, extension, category.
    • numeric: measurements like loc, bytes, score, count.
    • date: date/time columns.
    • links: URL columns.
    • image: image URL/path columns.
    • geospatial: geographic columns (e.g. a lat/lon pair).
    • coordinate1 / coordinate2: precomputed x / y layout coordinates to place points directly.
    • vector: precomputed embedding-vector columns.
    • custom-model: columns embedded with a custom model.
    • connection: columns linking points to each other.
    • ignored columns go in --delete-column.

    The --*-column flags cover all of the backend's supported types. For anything unusual, --data-types <json> passes a raw data_types array straight through.

  3. Ask where to put the map if the user did not specify:
    • new space
    • existing space
  4. Run mantis create map with explicit flags. Example:
mantis create map "./dataset.csv" \
  --space-mode new \
  --space-name "Codebase Index" \
  --private \
  --map-name "Source Files" \
  --title-column "path" \
  --semantic-column "summary,content" \
  --categoric-column "language,kind,extension" \
  --numeric-column "loc,bytes" \
  --activate \
  --thread-name "Dataset Exploration"

For an existing space:

mantis create map "./dataset.csv" \
  --space-mode existing \
  --space-id "<space-uuid>" \
  --map-name "Source Files" \
  --title-column "path" \
  --semantic-column "summary,content"
  1. Report the created space link and map id from the JSON output.

Notes

  • If the user wants a fully interactive human flow, run only mantis create map "./dataset.csv".
  • If an agent is driving the flow, avoid interactive prompts by passing flags.
  • Use mantis setup first if the CLI says API key or URL is missing.

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