agentleFS
Sign inStart free
OpenLinkSoftwareOpenLinkSoftware/ai-agent-skills/csv-to-rdf-det-generator/SKILL.md

csv-to-rdf-det-generator

Skill42 starsChanged 51 days agoMITView on GitHub

Create or update a custom DAV DET that accepts CSV uploads, transforms them to RDF, and then writes to the Quad Store. Use when the task is to scaffold, modify, or document a CSV-backed ingestion DET with DAV hook functions, CSV-to-RDF mapping logic, graph assignment rules, verification SQL, SPARQL checks, and packaging notes.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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. Distinctive:

    Use this skill when building a DAV DET that ingests CSV, transforms it to RDF, and persists the result to the Quad Store.

    line 8
  2. Distinctive:

    Use this skill when the user asks to:

    line 20
  3. Distinctive:

    create a CSV ingestion DET

    line 22
  4. Distinctive:

    treat CSV transformation as an explicit step before Quad Store upload

    line 41
  5. Distinctive:

    keep mapping assumptions documented

    line 43
  6. Very specific:

    ensure _DAV_DIR_LIST returns a proper array of DAV rows

    line 44

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

CSV to RDF DET Generator

Use this skill when building a DAV DET that ingests CSV, transforms it to RDF, and persists the result to the Quad Store.

What This Skill Produces

  • DET SQL scaffolding for CSV ingestion
  • guidance for CSV-to-RDF transformation flow before Quad Store load
  • graph assignment and metadata persistence rules
  • verification SQL and SPARQL probes
  • packaging guidance for Virtuoso source and VAD trees

Trigger Conditions

Use this skill when the user asks to:

  • create a CSV ingestion DET
  • transform CSV to RDF before graph load
  • build a WebDAV-backed CSV-to-RDF pipeline
  • scaffold DAV hooks for CSV uploads with Quad Store side effects

Workflow

⛔ PRE-BUILD CHECK: Before producing output, re-read the relevant workflow section above and re-read any checklists or verification gates defined in this skill. Confirm each checklist item before writing output. Build to pass — do not retro-fit. Apply the CLAUDE.md Anti-Drift Protocol: re-read spec section before build, gate-first validation, section-by-section delivery.

  1. Identify the DET name, CSV shape, and target RDF model.
  2. Define graph assignment rules and mapping strategy.
  3. Load references/det-hook-checklist.md.
  4. Load references/csv-to-rdf-pipeline.md.
  5. Load references/csv-mapping-design.md.
  6. Generate or update runtime SQL using references/csv-det-template.md.
  7. Generate validation SQL, SPARQL, and WebDAV probes from references/verification-queries.md.

Output Requirements

  • treat CSV transformation as an explicit step before Quad Store upload
  • define how headers, datatypes, IRIs, and row identity are derived
  • keep mapping assumptions documented
  • ensure _DAV_DIR_LIST returns a proper array of DAV rows

References

  • references/det-hook-checklist.md
  • references/csv-to-rdf-pipeline.md
  • references/csv-mapping-design.md
  • references/csv-det-template.md
  • references/verification-queries.md

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