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

rdf-det-variant-generator

Skill42 starsChanged 51 days agoMITView on GitHub

Create or update a custom DAV DET variant based on RDF Import DET for Virtuoso. Use when the task is to scaffold, modify, or document a DET that ingests RDF documents into the Quad Store, supports one or more Virtuoso-supported RDF document types, implements the required _DAV_* hook family, or needs verification SQL, WebDAV probes, and VAD/source integration notes.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Use this skill when building a custom DAV DET derived from the RDFImport pattern for RDF-bearing document types supported by Virtuoso.

    line 8
  2. Distinctive:

    Use this skill when the user asks to:

    line 22
  3. Distinctive:

    create a DET similar to RDF Import

    line 24
  4. Distinctive:

    create or update DET SQL hooks and validation queries

    line 28
  5. Very specific:

    Use references/rdf-det-template.md to generate or update the DET.

    line 38
  6. Distinctive:

    Keep runtime SQL in Virtuoso procedure form.

    line 44
  7. Distinctive:

    Keep verification artifacts separate from runtime code.

    line 45
  8. Distinctive:

    When generating listing logic, prefer explicit vector accumulation unless there is a proven reason to use builder helpers.

    line 46
  9. Very specific:

    Ensure the DET returns a proper array of DAV row vectors from _DAV_DIR_LIST.

    line 47

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

RDF DET Variant Generator

Use this skill when building a custom DAV DET derived from the RDFImport pattern for RDF-bearing document types supported by Virtuoso.

What This Skill Produces

  • DET SQL scaffolding derived from RDFImport
  • Hook coverage checklist for required DB.DBA.<DetName>_DAV_* functions
  • Variants for multiple RDF document types
  • Verification SQL and WebDAV probes
  • Packaging guidance for:
    • {HOME}/Documents/Management/Development/virtuoso-engine/binsrc/yacutia/sql/
    • {HOME}/Documents/Management/Development/ods-virtuoso/briefcase/sql/

Trigger Conditions

Use this skill when the user asks to:

  • create a DET similar to RDF Import
  • support additional RDF document types
  • generate a new Quad Store ingestion DET
  • scaffold a DAV DET that loads RDF into named graphs
  • create or update DET SQL hooks and validation queries

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, target folders, and desired graph behavior.
  2. Confirm the RDF document types to support.
  3. Load the implementation checklist in references/det-hook-checklist.md.
  4. Load the RDF-type guidance in references/virtuoso-rdf-doc-types.md.
  5. Use references/rdf-det-template.md to generate or update the DET.
  6. Generate validation queries from references/verification-queries.md.
  7. Provide VAD/source integration notes and release/build reminders.

Output Requirements

  • Keep runtime SQL in Virtuoso procedure form.
  • Keep verification artifacts separate from runtime code.
  • When generating listing logic, prefer explicit vector accumulation unless there is a proven reason to use builder helpers.
  • Ensure the DET returns a proper array of DAV row vectors from _DAV_DIR_LIST.

References

  • references/det-hook-checklist.md
  • references/virtuoso-rdf-doc-types.md
  • references/rdf-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