semantica

Installation
SKILL.md

Semantica

Instructions

  1. Select the task layer first: package API, semantica CLI, standalone server/worker/explorer, MCP, or a specific optional connector. Confirm the exact extra and backend from the pinned pyproject.toml before proposing installs.
  2. Treat commands and data flow as scoped examples; inspect installed CLI help/source for exact syntax. Build a minimal environment and add only the extra required. Avoid [all] unless user explicitly requests the broad dependency set and accepts its footprint.
  3. Before configuring a model/provider, database, cloud service, or MCP client, obtain explicit approval for credential use, external calls, uploads, cost, data access, and configuration changes. Never ask for or print secret values; prefer documented environment/config references and local endpoints where appropriate.
  4. Distinguish package graph-store backends (e.g. Neo4j/FalkorDB/Neptune/AGE) from the overall toolkit. Explain connector prerequisites and distinguish offline code inspection from runtime, service, or provider verification.

Examples

  • “Which Semantica extras do I need to ingest documents and store triples in Oxigraph?”
  • “Trace this Semantica CLI/MCP startup failure without using credentials.”
  • “Plan a minimal local pipeline for parsing and entity extraction.”

Best practices

Installs
2
GitHub Stars
60
First Seen
Oct 28, 2026