Goga Brainstorm Contracts Usages Inline
Connecting header Usages for a single cell in the brainstorm contracts pipeline
Install
$ agentstack add skill-qarium-goga-goga-brainstorm-contracts-usages-inline ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-qarium-goga-goga-brainstorm-contracts-usages-inline) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
goga-brainstorm-contracts-usages-inline
Algorithm
Connect every practice the cell consumes into its CODEMANIFEST header.
- Syntax and semantics of the
UsagesandImports.Usagesdirectives (keys, paths, aliasing, conflict rules)
follow goga-cell.
- The choice of connection form (file / URL / inline) and when a practice is worth declaring follow
goga-cookbook.
Step 1 — Collect what the cell consumes
Build the factual basis for all three categories from the reports:
- From
[CELL_DISTRIBUTION_REPORT]— the types this cell imports from other cells (inter-cellImports). - From
[TYPE_DETAIL_REPORT]— each type's responsibility, signatures, and interactions; identify the **external
libraries, patterns, and formats** the types rely on.
Step 2 — Base usages
Take all base usages from goga-codemanifest-base as-is and add them to the Usages directive unchanged. Where a base practice constrains the contract form (error style, naming, pattern), the contract must comply — flag it so the annotations step enforces it.
Step 3 — Cross-cell usages
For every type imported from another cell (Step 1): if the provider cell has .usages/ files describing how to work with that type's API, connect them via Imports.Usages. Resolve any name clash with a local Usages key through the AS alias (goga-cell). These document the provider's facade — they do not impose obligations on this contract.
Step 4 — External usages
For every external library, pattern, or format the cell relies on (Step 1): look for an existing usage file in .goga/usages/ or .goga/usages/cooks/. If found, connect it via Usages in the form goga-cookbook prescribes for the situation. If none exists, record it in External Usage Gaps.
Return
Return the connected base / cross-cell / external usages and the set of Usages keys (the backtick targets the annotations step references).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: qarium
- Source: qarium/goga
- License: BSD-3-Clause
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.