Iptvnator Sqlite DB Worker
4gray/iptvnator
A skill your agent uses when changing Electron SQLite IPC, database-worker operations, request-scoped progress or cancellation, worker packaging, or runtime verification of non-EPG database work.
Houndarr's SQLite schema and migration discipline. An agent skill from av1155/houndarr.
Install Houndarr Database
$ npx skills add av1155/houndarr --skill houndarr-database -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install av1155/houndarr houndarr-database --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/av1155/houndarr.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/houndarr-database .claude/skills/houndarr-database && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "houndarr-database" agent skill from https://github.com/av1155/houndarr/tree/main/.agents/skills/houndarr-database into .claude/skills/houndarr-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "houndarr-database", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/av1155/houndarr/tree/main/.agents/skills/houndarr-databaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add av1155/houndarr --skill houndarr-database -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install av1155/houndarr houndarr-database --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/av1155/houndarr.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/houndarr-database .agents/skills/houndarr-database && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "houndarr-database" agent skill from https://github.com/av1155/houndarr/tree/main/.agents/skills/houndarr-database into .agents/skills/houndarr-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "houndarr-database", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add av1155/houndarr --skill houndarr-database -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install av1155/houndarr houndarr-database --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/av1155/houndarr.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/houndarr-database .cursor/skills/houndarr-database && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "houndarr-database" agent skill from https://github.com/av1155/houndarr/tree/main/.agents/skills/houndarr-database into .cursor/skills/houndarr-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "houndarr-database", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/av1155/houndarr.git --path .agents/skills/houndarr-database--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add av1155/houndarr --skill houndarr-database -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install av1155/houndarr houndarr-database --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/av1155/houndarr.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/houndarr-database .gemini/skills/houndarr-database && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "houndarr-database" agent skill from https://github.com/av1155/houndarr/tree/main/.agents/skills/houndarr-database into .gemini/skills/houndarr-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "houndarr-database", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install av1155/houndarr houndarr-databaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add av1155/houndarr --skill houndarr-database -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/av1155/houndarr.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/houndarr-database .github/skills/houndarr-database && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "houndarr-database" agent skill from https://github.com/av1155/houndarr/tree/main/.agents/skills/houndarr-database into .github/skills/houndarr-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "houndarr-database", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add av1155/houndarr --skill houndarr-database -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install av1155/houndarr houndarr-database --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/av1155/houndarr.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/houndarr-database .opencode/skills/houndarr-database && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "houndarr-database" agent skill from https://github.com/av1155/houndarr/tree/main/.agents/skills/houndarr-database into .opencode/skills/houndarr-database/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "houndarr-database", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
houndarr-database- GitHub stars
- 292
- Token cost
- ~811 tokens
- SKILL.md length
- 347 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Houndarr's SQLite schema and migration discipline. An agent skill from av1155/houndarr.
- Works in 6 steps: Bump SCHEMA_VERSION at the top of… → Add a _migrate_to_vN(conn) function that… → If the migration renames a value used in… → …
- Databases work in your project
- SKILL.md covers Database basics, Schema reference, Migration constants are… and Schema bump checklist
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Houndarr Database is an agent skill from av1155/houndarr. Houndarr's SQLite schema and migration discipline. Loads when reading or editing src/houndarr/database.py. Covers the schema table reference, the SCHEMAVERSION bump checklist, and the version-locking rule for migration constants that prevents later renames from retroactively breaking earlier rebuild migrations.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Databases. It works with SQLite. The repository describes itself as: Self-hosted arr companion for controlled missing, cutoff, and upgrade searches. The licence is AGPL-3.0.
When your agent uses it
- Databases work in your project
Example prompts
- “/houndarr-database”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Bump SCHEMA_VERSION at the top of database.py.
- Add a _migrate_to_vN(conn) function that performs the migration.
- If the migration renames a value used in CHECK constraints, introduce
- Add an entry to _MIGRATIONS keyed by the new version.
- Update _SCHEMA_SQL if the canonical fresh-install DDL changed.
- Add tests under tests/test_database/ covering the migration path.
What it can do on your machine
Read from SKILL.md and the folder at commit 9b39fdb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Houndarr Database loads about 811 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 347 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from av1155/houndarr at commit 9b39fdb, republished under its AGPL-3.0 licence (© av1155). 347 words, ~811 tokens.
Download SKILL.mdSave it as
.claude/skills/houndarr-database/SKILL.md (or your agent's skills folder).- name
- houndarr-database
- description
- Houndarr's SQLite schema and migration discipline. Loads when reading or editing src/houndarr/database.py. Covers the schema table reference, the SCHEMA_VERSION bump checklist, and the version-locking rule for migration constants that prevents later renames from retroactively breaking earlier rebuild migrations.
- paths
- src/houndarr/database.py
Houndarr database conventions
Database basics
SQLite via aiosqlite. get_db() is an async context manager that opens
a fresh connection per call (FKs enabled per connection; WAL mode set
once in init_db()). Schema version is currently 19. Bump
SCHEMA_VERSION and add a _migrate_to_vN when changing schema.
Schema reference
| Table | Purpose | Key constraints |
|---|---|---|
settings | Key-value config store | key TEXT PK |
widget_api_key | External widget API key, single row (v19) | id INTEGER PRIMARY KEY CHECK(id = 1); hash is SHA-256 hex digest with CHECK(length(hash) = 64 AND hash NOT GLOB '*[^0-9a-f]*'); no FK |
instances | *arr instance configs | type CHECK IN ('radarr','sonarr','lidarr','readarr','whisparr_v2','whisparr_v3'); many policy columns with CHECK constraints; monitored_total / unreleased_count / snapshot_refreshed_at populated by the supervisor's snapshot refresh task |
cooldowns | Per-item search cooldown tracking | instance_id FK→instances ON DELETE CASCADE; UNIQUE(instance_id, item_id, item_type); search_kind CHECK IN ('missing','cutoff','upgrade') (v15) |
search_log | Audit trail | instance_id FK→instances ON DELETE SET NULL; action CHECK IN ('searched','skipped','error','info') |
Full DDL and migrations live in src/houndarr/database.py.
Migration constants are version-locked
Rebuild migrations (CREATE TABLE foo_new ... INSERT INTO foo_new SELECT ...)
must reference a snapshot constant frozen at the introducing schema version,
never the current _ITEM_TYPES / _INSTANCE_TYPES alias. The snapshots
(_ITEM_TYPES_V5, _ITEM_TYPES_V10, _ITEM_TYPES_V15, _ITEM_TYPES_V16,
_INSTANCE_TYPES_V5, _INSTANCE_TYPES_V10) live at the top of database.py
and are immutable after their migration ships. Fresh-install DDL in
_SCHEMA_SQL uses the latest snapshot via the _ITEM_TYPES /
_INSTANCE_TYPES aliases.
When adding a migration that renames a value: introduce a new
_FOO_TYPES_VN constant, point the _FOO_TYPES alias at it, write the new
migration with the new constant plus a CASE WHEN translation in its COPY,
and leave the prior snapshot (and prior migrations) untouched. This prevents
the class of bug where a later rename retroactively breaks an earlier
rebuild migration's CHECK clause.
Schema bump checklist
- Bump
SCHEMA_VERSIONat the top ofdatabase.py. - Add a
_migrate_to_vN(conn)function that performs the migration. - If the migration renames a value used in CHECK constraints, introduce
a fresh
_FOO_TYPES_VNsnapshot and reference it in the new migration. - Add an entry to
_MIGRATIONSkeyed by the new version. - Update
_SCHEMA_SQLif the canonical fresh-install DDL changed. - Add tests under
tests/test_database/covering the migration path.
© av1155, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/houndarr-database of av1155/houndarr.
Open the folder on GitHubat commit 9b39fdb
Compare with similar skills
Houndarr Database next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Houndarr Database this skillav1155/houndarr | 292 | — | ~811 | Automated safety check: Pass | AGPL-3.0 | |
| Iptvnator Sqlite DB Worker4gray/iptvnator | 7.3k | — | ~824 | Automated safety check: Pass | MIT | |
| Analyze Nsys Profilemlc-ai/pith-train | 355 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Reactive Sqlite UIfastrepl/anarlog | 9.5k | — | ~699 | Automated safety check: Pass | MIT | |
| Composer Forensicsdxos/dxos | 525 | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Sqlite Schema Designfastrepl/anarlog | 9.5k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Analyze Nsys Profile
mlc-ai/pith-train
Query a captured PithTrain Nsight Systems profile to measure compute/communication overlap, locate exposed comm by DualPipeV stage, and inspect per-rank stream behavior.
Reactive Sqlite UI
fastrepl/anarlog
Build SQLite-backed reactive UI in apps/desktop using stable patterns for reads, selection, forms, writes, and loading states.
Composer Forensics
dxos/dxos
Forensically inspect and repair Composer browser profiles — offline (Chrome OPFS / SQLite extract) or live via /recovery.html debug port.
Sqlite Schema Design
fastrepl/anarlog
Design or review schemas for crates/cloudsync using SQLite Sync constraints, not generic SQLite advice.
Makemigrations
deusXmachina-dev/memorylane
Create SQLite migrations for MemoryLane storage schema changes.
More from av1155/houndarr
All 9 skills in this repoBump
av1155/houndarr
Bump Houndarr version and prepare a release PR. An agent skill from av1155/houndarr.
Check
av1155/houndarr
Run Houndarr's full quality gate (ruff lint, ruff format check, mypy, bandit, pytest) and report results in a single table.
Houndarr Architecture
av1155/houndarr
Houndarr's source layout and architectural patterns at file granularity.
Houndarr Changelog
av1155/houndarr
Houndarr's CHANGELOG.md style guide and entry rules. An agent skill from av1155/houndarr.
Houndarr Testing
av1155/houndarr
Houndarr's pytest patterns. An agent skill from av1155/houndarr.
Verify Algorithms
av1155/houndarr
Verify probabilistic, distributional, or random behaviour empirically before changing search-engine code.
Related
Works with
Categories
Questions about Houndarr Database
What does Houndarr Database do?
Houndarr's SQLite schema and migration discipline. An agent skill from av1155/houndarr. Houndarr Database is an agent skill from av1155/houndarr. Houndarr's SQLite schema and migration discipline.
When should I use Houndarr Database?
Houndarr Database fits situations like: databases work in your project.
How do I install Houndarr Database in Claude Code?
Run `npx skills add av1155/houndarr --skill houndarr-database -a claude-code`. Or copy the skill folder (.agents/skills/houndarr-database in av1155/houndarr) into .claude/skills/houndarr-database in your project. Claude Code loads it when a task matches its description.
How do I install Houndarr Database in Codex?
Run `npx skills add av1155/houndarr --skill houndarr-database -a codex`. Or copy the skill folder (.agents/skills/houndarr-database in av1155/houndarr) into .agents/skills/houndarr-database in your project. Codex loads it when a task matches its description.
Can I use Houndarr Database in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add av1155/houndarr --skill houndarr-database -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/houndarr-database, .gemini/skills/houndarr-database, .github/skills/houndarr-database and .opencode/skills/houndarr-database in your project.
What does Houndarr Database need to run?
SKILL.md names no scripts, command-line tools or credentials: Houndarr Database is instructions for the agent only.
Does Houndarr Database access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Houndarr Database safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Houndarr Database use?
Houndarr Database is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Houndarr Database use?
About 811 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Houndarr Database?
Skills that share tags, products or a category with Houndarr Database: Iptvnator Sqlite DB Worker (4gray/iptvnator, 7.3k stars), Analyze Nsys Profile (mlc-ai/pith-train, 355 stars), Reactive Sqlite UI (fastrepl/anarlog, 9.5k stars) and Composer Forensics (dxos/dxos, 525 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Houndarr Database?
av1155 (a GitHub user) maintains it in av1155/houndarr, which has 292 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 5, 2026.
Source: av1155/houndarr on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.