Skip to content
Skills Library
DevOps & cloud · Automation

opsquire

/opsquire

Use for ANY tooling need: a script, check, query, deploy, restart, install, report, or repeated procedure, especially anything touching hosts, production systems, credentials or live services. Opsquire is the operator's tool where agents prepare scripts and the operator runs them with one command, with a permanent record. Use it before writing any ad-hoc script or handing over shell commands.

Repository
opsquire ↗
Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

82/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content17 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use for ANY tooling need: a script, check, query, deploy, restart, install, report, or repeated procedure, especially anything touching hosts, production systems, credentials or live services. Opsquire is the operator's tool where agents prepare scripts and the operator runs them with one command, with a permanent record. Use it before writing any ad-hoc script or handing over shell commands.

Original author description

Use for ANY tooling need: a script, check, query, deploy, restart, install, report, or repeated procedure, especially anything touching hosts, production systems, credentials or live services. Opsquire is the operator's tool where agents prepare scripts and the operator runs them with one command, with a permanent record. Use it before writing any ad-hoc script or handing over shell commands.

How it works

SKILL.md has no level-two headings · 24 lines, 299 words

SKILL.md preview
---
name: opsquire
description: Use for ANY tooling need: a script, check, query, deploy, restart, install, report, or repeated procedure, especially anything touching hosts, production systems, credentials or live services. Opsquire is the operator's tool where agents prepare scripts and the operator runs them with one command, with a permanent record. Use it before writing any ad-hoc script or handing over shell commands.
---

The operator runs all tooling through Opsquire. Agents prepare; the operator runs; every run is recorded.
If your shell says `opsquire: command not found`, call it as `{{opsquire_command}}`; the commands you hand the operator
stay `opsquire ...`.

1. Run `opsquire home` to find the home, then read `<home>/AGENTS.md` (the contract, including the operator's local
   rules) and `<home>/docs/CATALOG.md` (everything that already exists). Follow the contract exactly; it wins over
   this summary.
2. Search before writing: `opsquire find <keywords>`. Reuse a task or a general script; create a task with
   `opsquire new` only when nothing fits, and interview the operator first (one question at a time, each with a
   recommended answer) when something new must be built.
3. Independent pieces (none needs another's result, no shared general script) are built at the same time: open one
   piece per part with `opsquire piece open <name> --request "..." --json`, start one subagent per piece with the
   printed brief (it works under the piece's path and env and builds only its piece), then `opsquire piece land
   <name>` each one as it reports. Read-only research can go to subagents without a piece.
4. `opsquire lint <task>` must pass (ruff, mypy --strict, shellcheck, and the task's unit tests).
5. Never run `opsquire run` yourself for work that needs what agents must not reach (production, ssh,
   credentials); hand the operator the exact command, one per step: `opsquire run <task>` first (dry or read),
   then `opsquire run <task> --apply`. When the task already exists (reused, already run, or closed), also run
   `opsquire handover <task> [--apply] --why "one line"` so that run reaches the operator's inbox.
6. Then run `opsquire wait <task> --json` and continue from the run record. Never ask the operator to paste output.

Purely local work (editing code, tests, analysing local files) needs no Opsquire task.

Versions

The database has no other skills named opsquire.

Database snapshot: 13.11.2026 · package version 2cfad8079afa (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90ansible-configure-vm
    Configure VMs with Ansible playbooks and ad-hoc commands. Run playbooks, install Galaxy roles, ad-hoc modules, inventory management, check mode. Use when configuring VMs or running Ansible against hosts.
  • 100build-deploy-and-tooling
    Use when writing, reviewing, or changing build scripts, CI workflows, deploy pipelines, repo setup, or evaluating a new tool/dependency
  • 95ml4t-research-operator
    Thin autonomous research operator pattern for ML4T experiments. Use when an agent should inspect artifacts, read skills, run scripts, and produce an auditable recommendation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.