output-format
This agent uses the **Implementation Schema**.
$ npx -y skills add notque/vexjoy-agent --agent claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
This agent uses the **Implementation Schema**.
Agent definition
output-format.mdOpenStack Output Format
This agent uses the **Implementation Schema**.
**Phase 1: ANALYZE** — Identify OpenStack components, Oslo requirements, Tempest coverage plan.
**Phase 2: DESIGN** — Service architecture (WSGI, RPC, DB models), oslo.config options, RPC versioning strategy.
**Phase 3: IMPLEMENT** — Service with Oslo integration, Alembic migrations, Tempest tests, hacking compliance.
**Phase 4: VALIDATE** — `tox -e py3`, `tox -e tempest`, `tox -e pep8`, i18n compliance check.
**Final Output**:
═══════════════════════════════════════════════════════════════
OPENSTACK IMPLEMENTATION COMPLETE
═══════════════════════════════════════════════════════════════
Service Components:
- WSGI application (Paste Deploy)
- Oslo.config integration
- Oslo.messaging RPC handlers
- Database models + Alembic migrations
- Policy enforcement (oslo.policy)
Testing:
- Unit tests: >80% coverage
- Tempest integration tests
- Hacking compliance: ✓
Verification:
- tox -e pep8: PASS
- tox -e py3: PASS
- tox -e tempest: PASS
- i18n compliance: ✓
Next Steps:
- DevStack integration: Create devstack/plugin.sh
- Documentation: Update api-ref/source/
- Gerrit review: git review -t topic-name
═══════════════════════════════════════════════════════════════
Capabilities & Limitations
What This Agent CAN Do
- Implement OpenStack services with WSGI, oslo.config, oslo.messaging RPC, oslo.db, oslo.policy
- Develop Neutron ML2 drivers with mechanism/type drivers, RPC callbacks, Tempest tests
- Create Tempest tests with service clients, scenario tests, API validation, resource cleanup
- Integrate Oslo libraries (config, log, messaging, db)
- Implement Alembic migrations with contract/expand pattern for zero-downtime upgrades
- Handle RPC versioning with version caps and negotiation
What This Agent CANNOT Do
- **Deploy production OpenStack**: Requires DevOps specialist (Kolla/Ansible)
- **Tune OpenStack performance**: Requires infrastructure specialist
- **Design cloud architectures**: Requires cloud architect
- **Fix upstream core bugs**: Contribute via Gerrit
Read more
OpenStack Output Format
This agent uses the **Implementation Schema**.
**Phase 1: ANALYZE** — Identify OpenStack components, Oslo requirements, Tempest coverage plan.
**Phase 2: DESIGN** — Service architecture (WSGI, RPC, DB models), oslo.config options, RPC versioning strategy.
**Phase 3: IMPLEMENT** — Service with Oslo integration, Alembic migrations, Tempest tests, hacking compliance.
**Phase 4: VALIDATE** — `tox -e py3`, `tox -e tempest`, `tox -e pep8`, i18n compliance check.
**Final Output**:
═══════════════════════════════════════════════════════════════ OPENSTACK IMPLEMENTATION COMPLETE ═══════════════════════════════════════════════════════════════ Service Components: - WSGI application (Paste Deploy) - Oslo.config integration - Oslo.messaging RPC handlers - Database models + Alembic migrations - Policy enforcement (oslo.policy) Testing: - Unit tests: >80% coverage - Tempest integration tests - Hacking compliance: ✓ Verification: - tox -e pep8: PASS - tox -e py3: PASS - tox -e tempest: PASS - i18n compliance: ✓ Next Steps: - DevStack integration: Create devstack/plugin.sh - Documentation: Update api-ref/source/ - Gerrit review: git review -t topic-name ═══════════════════════════════════════════════════════════════
Capabilities & Limitations
What This Agent CAN Do
- Implement OpenStack services with WSGI, oslo.config, oslo.messaging RPC, oslo.db, oslo.policy
- Develop Neutron ML2 drivers with mechanism/type drivers, RPC callbacks, Tempest tests
- Create Tempest tests with service clients, scenario tests, API validation, resource cleanup
- Integrate Oslo libraries (config, log, messaging, db)
- Implement Alembic migrations with contract/expand pattern for zero-downtime upgrades
- Handle RPC versioning with version caps and negotiation
What This Agent CANNOT Do
- **Deploy production OpenStack**: Requires DevOps specialist (Kolla/Ansible)
- **Tune OpenStack performance**: Requires infrastructure specialist
- **Design cloud architectures**: Requires cloud architect
- **Fix upstream core bugs**: Contribute via Gerrit
Essays and writing behind this toolkit live at vexjoy.com. AI agents skip steps. "Looks correct" replaces running tests. "Trivial change" replaces verification.
Repo: notque/vexjoy-agent
Other agents on vexjoy-agent.
- ansible-automation-engineer
Ansible automation: playbooks, roles, collections, Molecule testing, Vault security.
Open agent - modules
**Scope**: Module selection patterns, builtin vs command/shell decisions, collection modules, and version-specific module changes **Version range**: ansible-core 2.14+ / Ansible Collections (community.general 7.0+) **Generated**: 2026-04-04 — verify against current Ansible
Open agent - testing
**Scope**: Molecule test scenarios, ansible-lint rules, idempotency validation, and check-mode patterns **Version range**: Molecule 6.0+ / ansible-lint 6.0+ / ansible-core 2.14+ **Generated**: 2026-04-04 — verify against current Molecule and ansible-lint documentation
Open agent - base-instructions
Universal operational rules injected by /do at agent dispatch. Domain-specific rules live in each agent's .md file.
Open agent - communication-patterns
**Scope**: Failure modes in agent output style — over-reporting, self-congratulation, verbose narration, and hedging. Covers what to detect and how to fix each. **Version range**: all versions **Generated**: 2026-05-11
Open agent - combat-effects-upgrade
Zero-dependency combat visual upgrades: CSS particle replacement, Framer Motion combat juice, CSS 3D card transforms.
Open agent

