agentleFS
Sign inStart free
IvanLi-CNIvanLi-CN/agent-toolkit/skills/tavily-hikari-infra/SKILL.md

tavily-hikari-infra

Skill0 starsChanged 18 days agoMITView on GitHub

Inspect a configured Tavily Hikari primary/standby deployment through read-only checks.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Use only read-only inventory, status and log commands.

    line 22

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

Tavily Hikari infrastructure

This Skill contains a configuration-driven read-only inventory and HA runbook. It deliberately stores no host inventory, resolved address, private domain, credential or owner-only deployment record.

Configuration

  • TAVILY_PRIMARY_ALIAS and TAVILY_STANDBY_ALIAS select SSH aliases.
  • TAVILY_PRIMARY_COMPOSE selects the primary Compose file when applicable.
  • TAVILY_STANDBY_SERVICE selects the standby service unit.
  • TAVILY_STANDBY_URL is an optional public health origin configured out of band.
  • TAVILY_CONFIG_DIR or TAVILY_HOSTS_FILE selects the protected local inventory; it defaults to ${XDG_CONFIG_HOME:-$HOME/.config}/tavily-hikari-infra/hosts.txt.

Copy references/hosts.txt.example into that protected directory when setting up a deployment. Keep any local inventory based on references/inventory.md.example outside the checkout. The helper never reads inventory from the checkout. Connection details belong in the operator's SSH configuration. Missing or ambiguous values fail closed.

Guardrails

Use only read-only inventory, status and log commands. Any future mutating action must require an explicit --yes and a separate authorization. Keep tokens and release credentials outside the repository. Redact resolved hostnames, addresses and response bodies before sharing.

Commands

scripts/tavily-hikari-infra inventory
scripts/tavily-hikari-infra status <primary|standby>
scripts/tavily-hikari-infra logs <primary|standby> --tail 200

See the generic runbook and the standby environment template.

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