@sdemyanov/schema
BUse this skill when creating, inspecting, or migrating Retriever's SQLite schema. It is the source of truth for table layouts, path rules, custom field registry behavior, manual field locks, and schema-version behavior.
Install
agr install @sdemyanov/schema --target claudeWrites 2 files into .claude/skills/, pinned to git-e5748c73.
- .claude/skills/schema/SKILL.md
- .claude/skills/schema/schema.md
Document
name: schema description: > Use this skill when creating, inspecting, or migrating Retriever's SQLite schema. It is the source of truth for table layouts, path rules, custom field registry behavior, manual field locks, and schema-version behavior. metadata: version: "1.1.17"
Operates under
retriever:routing. If the user's intent actually fits a different tier — anotherretriever:*skill, a Tier 2 slash, a Tier 3tools.pysubcommand, or (last resort) direct DB access — stop and re-route against the ladder before continuing.
Retriever Schema
Use this skill whenever a task touches:
- SQLite table definitions
- schema migrations
- relative path rules
- preview records
- chunk storage
- custom field registry entries
- manual-value overwrite protection rules
- structured filter validation rules
Required references
- Treat ../tool-template/src/10_core.py, ../tool-template/src/40_schema_runtime.py, and the generated ../tool-template/tools.py as the current source of truth.
- Use
python3 skills/tool-template/tools.py schema-versionto confirm the currentschema_versionandtool_version. - Read schema.md for background terminology only; if it conflicts with the source fragments or
schema-version, the code wins.
Rules
- Do not invent new table names when an existing table fits the need.
- Keep document paths relative to the workspace root.
- Keep preview paths relative to
.retriever/. - Preserve manual edits by locking corrected document fields until explicitly overwritten.
- Prefer structured filter contracts over raw SQL filter strings.
- Make migrations idempotent.
- Prefer additive schema changes over destructive rewrites.
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-e5748c73d16d2026-07-31