New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Hydra Architect

by streamband in streamband/hydra-srt

A skill your agent uses when designing or evolving Hydra platform architecture across Elixir/Phoenix, SQLite, VictoriaMetrics/VictoriaLogs analytics, native/Rust, and runtime boundaries.

Apache-2.0Auto-check passedDatabases

Install Hydra Architect

skills CLI
$ npx skills add streamband/hydra-srt --skill hydra-architect -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install streamband/hydra-srt hydra-architect --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/streamband/hydra-srt.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/hydra-architect .claude/skills/hydra-architect && rm -rf skills-src

Use ~/.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/

Facts

Skill name
hydra-architect
GitHub stars
146
Token cost
~1.2k tokens
SKILL.md length
553 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when designing or evolving Hydra platform architecture across Elixir/Phoenix, SQLite, VictoriaMetrics/VictoriaLogs analytics, native/Rust, and runtime boundaries.

  • Works in 5 steps: Persist domain state in SQLite; do not… → Keep side effects at boundaries;… → Use Ecto.Multi or explicit transactions… → …
  • Evolving Hydra platform architecture across Elixir/Phoenix
  • SKILL.md covers When to use, Hydra-specific defaults, Non-negotiable principles and Decision policy (context over…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Hydra Architect is an agent skill from streamband/hydra-srt. Use when designing or evolving Hydra platform architecture across Elixir/Phoenix, SQLite, VictoriaMetrics/VictoriaLogs analytics, native/Rust, and runtime boundaries.

Its SKILL.md is about 1.2k 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, covering LLM observability. It works with SQLite, Elixir and Rust. The repository describes itself as: An Open Source Alternative to Haivision SRT Gateway. The licence is Apache-2.0.

When your agent uses it

  • Evolving Hydra platform architecture across Elixir/Phoenix
  • VictoriaMetrics/VictoriaLogs analytics
  • Runtime boundaries

Example prompts

  • “/hydra-architect”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Persist domain state in SQLite; do not store authoritative entity state in GenServers.
  2. Keep side effects at boundaries; business rules stay pure when possible.
  3. Use Ecto.Multi or explicit transactions for multi-step writes.
  4. Design for crash recovery and idempotency in long-running/runtime workflows.
  5. Every architecture change includes test strategy and rollback path.

What it can do on your machine

Read from SKILL.md and the folder at commit 8d081f2. 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

Hydra Architect loads about 1.2k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 553 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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 streamband/hydra-srt at commit 8d081f2, republished under its Apache-2.0 licence (© streamband). 553 words, ~1,171 tokens.

Download SKILL.mdSave it as .claude/skills/hydra-architect/SKILL.md (or your agent's skills folder).
name
hydra-architect
description
Use when designing or evolving Hydra platform architecture across Elixir/Phoenix, SQLite, VictoriaMetrics/VictoriaLogs analytics, native/Rust, and runtime boundaries.

Hydra Architect

When to use

Use this skill for architecture/design work in Hydra:

  • new subsystems and major refactors,
  • data model and migration strategy,
  • OTP lifecycle and process boundaries,
  • reliability/operability decisions,
  • implementation planning for coding agents.

Hydra-specific defaults

  • Primary source of truth: SQLite via Ecto (ecto_sqlite3).
  • Analytics sink: external VictoriaMetrics (route stats samples and route events over HTTP :8428) and VictoriaLogs (pipeline logs over HTTP :9428) — not transactional source of truth.
  • Control plane: Elixir/Phoenix.
  • Media/runtime work may involve native components and GStreamer.
  • Prefer incremental evolution over big-bang rewrites.

Non-negotiable principles

  1. Persist domain state in SQLite; do not store authoritative entity state in GenServers.
  2. Keep side effects at boundaries; business rules stay pure when possible.
  3. Use Ecto.Multi or explicit transactions for multi-step writes.
  4. Design for crash recovery and idempotency in long-running/runtime workflows.
  5. Every architecture change includes test strategy and rollback path.

Decision policy (context over dogma)

  • Ash/Oban/Broadway are optional tools, not mandatory defaults.
  • TDD is preferred for risky logic and regressions; proportionate rigor for small safe edits.
  • Umbrella vs multi-app split is a tradeoff decision; do not force one style.

Architecture workflow

  1. Confirm scope and constraints
  • Problem, success criteria, latency/reliability targets, migration risk.
  1. Map current system touchpoints
  • Read impacted modules, schemas, migrations, supervisors, API handlers, and tests.
  • Identify SQLite tables and any VictoriaMetrics/VictoriaLogs analytics coupling.
  1. Propose 1-2 viable designs
  • For each option: data flow, transaction boundaries, failure modes, observability, and cost.
  1. Choose and document one design
  • Record rationale and explicit tradeoffs.
  • List invariants that must remain true.
  1. Produce implementation plan
  • Small, reversible steps with validation after each step.
  • Include feature flag / staged rollout when risk is non-trivial.

SQLite guidance (Hydra)

  • Treat SQLite as authoritative operational state.
  • Keep migrations backward-compatible when feasible.
  • Avoid lock-heavy long transactions in hot paths.
  • Validate constraints at DB and changeset layers.
  • For backups/restore-sensitive changes, call out integrity implications explicitly.
Show full SKILL.md (242 more words)Show less

Victoria analytics guidance (Hydra)

  • Use VictoriaMetrics for historical route stats (hydra_srt_stats_sample) and route events (hydra_srt_route_event) via Prometheus remote-write style import and PromQL/Export APIs.
  • Use VictoriaLogs for pipeline log history via JSON-line ingest and LogSQL query APIs.
  • Analytics writes should be resilient to delay/retry; ingestion failures must not take down control-plane operations unless explicitly required.
  • VictoriaLogs retention is governed by server-side -retentionPeriod; there is no per-request delete API — plan resets around data-dir clears or retention changes.

OTP and runtime boundaries

  • GenServers are for orchestration, caches, buffering, and lifecycle control.
  • Domain truth lives in DB, not process memory.
  • Define restart semantics per child and expected recovery behavior.
  • Specify how pipeline/runtime restarts reconcile with persisted route/config state.

Required outputs for architecture tasks

For substantial architecture work, produce these artifacts (keep concise):

  1. Context: problem, constraints, non-goals.
  2. Option A/B: tradeoffs and failure modes.
  3. Chosen design: data model, boundaries, supervision impact.
  4. Plan: ordered implementation steps.
  5. Validation: tests, telemetry checks, and rollback strategy.

Review checklist

  • Clear ownership of authoritative state (SQLite vs in-memory vs Victoria analytics stores).
  • Transaction boundaries are explicit and safe.
  • Failure/retry/idempotency paths are defined.
  • Migration and rollback path are realistic.
  • Test plan covers regressions and concurrency-sensitive paths.
  • Operational signals (logs/metrics) are sufficient for debugging.

Anti-patterns to avoid

  • Treating Victoria analytics stores as system-of-record.
  • Hiding domain mutations in controllers/web layer.
  • Long blocking work in request path when async boundary is appropriate.
  • Large refactors without staged verification.
  • Architecture docs with no executable plan.

© streamband, Apache-2.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/hydra-architect of streamband/hydra-srt.

Open the folder on GitHubat commit 8d081f2

Compare with similar skills

Hydra Architect 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.

Hydra Architect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hydra Architect this skillstreamband/hydra-srt146—~1.2kAutomated safety check: PassApache-2.0
Fly Io DeployerLeoYeAI/openclaw-master-skills2.2k—~6.3kAutomated safety check: NotesMIT
Serviceradar Elixircarverauto/serviceradar921—~1.7kAutomated safety check: PassApache-2.0
Rust Heavy Performanceveloxbase/veloxdb646—~733Automated safety check: PassMIT
Elixir Expertpass-agent/loomkin1811 repos~796Automated safety check: PassMIT
Cdphuoshen80/ReinaManager693—~178Automated safety check: PassAGPL-3.0

Similar skills

  • Fly Io Deployer

    LeoYeAI/openclaw-master-skills

    Deploy and operate Node, Python, Go, Rust, Elixir, and Docker apps on Fly.io with production-grade fly.toml authoring, Machines API orchestration, region selection (latency vs sovereignty vs…

    2.2k GitHub stars~6.3k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check: notes

  • Serviceradar Elixir

    carverauto/serviceradar

    A skill your agent uses for ServiceRadar Elixir, Phoenix, LiveView, Ash/Ecto, migrations, external downloads, Hex dependencies, formatting, or Dialyzer work.

    921 GitHub stars~1.7k tokensUpdated yesterday
    DatabasesAuto-check passed

  • Rust Heavy Performance

    veloxbase/veloxdb

    Enforces a Rust-first approach for heavy work in VeloxDB so expensive compute stays in Tauri/Rust instead of JavaScript.

    646 GitHub stars~733 tokensUpdated 8 days ago
    DatabasesAuto-check passed

  • Elixir Expert

    pass-agent/loomkin

    Expert in Elixir, Phoenix Framework, and OTP. An agent skill from pass-agent/loomkin.

    181 GitHub starsUsed in 1 repo~796 tokens
    AI & LLM EngineeringAuto-check passed

  • Cdp

    huoshen80/ReinaManager

    通过 CDP 连接 ReinaManager WebView2，复现、诊断并验证真实应用的前端问题。仅在用户显式调用 /cdp 或 $cdp 进行前端调试时使用。

    693 GitHub stars~178 tokensUpdated 5 days ago
    DatabasesAuto-check passed

  • Migrate To Sqlite

    fastrepl/anarlog

    Migrate a TinyBase table to SQLite. An agent skill from fastrepl/anarlog.

    9.5k GitHub stars~2.1k tokensUpdated yesterday
    DatabasesAuto-check passed

More from streamband/hydra-srt

  • Elixir

    streamband/hydra-srt

    A skill your agent uses for Elixir/Phoenix development in this repo: implementing features, refactors, debugging, tests, Ecto changes, and production-safe fixes.

    146 GitHub stars~804 tokensUpdated 22 days ago
    Auto-check passed

  • Hydra Dev

    streamband/hydra-srt

    Run HydraSRT development workflows: mix q quality gate, Elixir unit/E2E tests, native Rust tests, web Vitest/Playwright, and make dev.

    146 GitHub stars~995 tokensUpdated 22 days ago
    Auto-check passed

  • Frontend

    streamband/hydra-srt

    A skill your agent uses for frontend work in webapp (React/TypeScript, UI implementation, tests, and refactors).

    146 GitHub stars~582 tokensUpdated 22 days ago
    Auto-check passed

  • Gstreamer

    streamband/hydra-srt

    A skill your agent uses for GStreamer pipeline development and debugging: graph design, caps negotiation issues, latency, synchronization, and runtime diagnostics.

    146 GitHub stars~499 tokensUpdated 22 days ago
    Auto-check passed

  • Hydra MCP

    streamband/hydra-srt

    Query the running HydraSRT instance via MCP (routes, logs, stats, control).

    146 GitHub stars~789 tokensUpdated 22 days ago
    Auto-check passed

  • Rust

    streamband/hydra-srt

    A skill your agent uses for Rust development in this repo: design, implementation, debugging, performance work, and reliable testing.

    146 GitHub stars~459 tokensUpdated 22 days ago
    Auto-check passed

Works with

Categories

Questions about Hydra Architect

What does Hydra Architect do?

A skill your agent uses when designing or evolving Hydra platform architecture across Elixir/Phoenix, SQLite, VictoriaMetrics/VictoriaLogs analytics, native/Rust, and runtime boundaries. Hydra Architect is an agent skill from streamband/hydra-srt. Use when designing or evolving Hydra platform architecture across Elixir/Phoenix, SQLite, VictoriaMetrics/VictoriaLogs analytics, native/Rust, and runtime boundaries.

When should I use Hydra Architect?

Hydra Architect fits situations like: evolving Hydra platform architecture across Elixir/Phoenix; victoriaMetrics/VictoriaLogs analytics; runtime boundaries.

How do I install Hydra Architect in Claude Code?

Run `npx skills add streamband/hydra-srt --skill hydra-architect -a claude-code`. Or copy the skill folder (.agents/skills/hydra-architect in streamband/hydra-srt) into .claude/skills/hydra-architect in your project. Claude Code loads it when a task matches its description.

How do I install Hydra Architect in Codex?

Run `npx skills add streamband/hydra-srt --skill hydra-architect -a codex`. Or copy the skill folder (.agents/skills/hydra-architect in streamband/hydra-srt) into .agents/skills/hydra-architect in your project. Codex loads it when a task matches its description.

Can I use Hydra Architect 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 streamband/hydra-srt --skill hydra-architect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hydra-architect, .gemini/skills/hydra-architect, .github/skills/hydra-architect and .opencode/skills/hydra-architect in your project.

What does Hydra Architect need to run?

SKILL.md names no scripts, command-line tools or credentials: Hydra Architect is instructions for the agent only.

Does Hydra Architect 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 Hydra Architect 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 Hydra Architect use?

Hydra Architect is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hydra Architect use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 Hydra Architect?

Skills that share tags, products or a category with Hydra Architect: Fly Io Deployer (LeoYeAI/openclaw-master-skills, 2.2k stars), Serviceradar Elixir (carverauto/serviceradar, 921 stars), Rust Heavy Performance (veloxbase/veloxdb, 646 stars) and Elixir Expert (pass-agent/loomkin, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hydra Architect?

streamband (a GitHub organization) maintains it in streamband/hydra-srt, which has 146 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 16, 2026.

Source: streamband/hydra-srt on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.