Goga Brainstorm Contracts Annotations
Writing annotations at all levels for a single cell in the brainstorm contracts pipeline
Install
$ agentstack add skill-qarium-goga-goga-brainstorm-contracts-annotations ✓ 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-annotations) 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-annotations
Algorithm
Write the implementation instructions for the given cell. Process every annotation target in order — cell header, then each Entity/Routine, then each method/property — and for each one:
- Determine the level: global (cell header), type-level (per
Entity/Routine), or member-level (per
method/property). The level selects the content — see goga-cookbook "When to write annotations". The global level additionally includes the base annotations from goga-codemanifest-base (the contract must comply with their constraints).
- Decide what content the annotation needs. Do not invent content — derive it:
- From
[TYPE_DETAIL_REPORT]— responsibility, signature (params and return), methods/properties, interactions. - From the usages-inline result — the connected Usages keys; place each on the level where the practice applies.
- From
goga-cookbook("Why") — the content categories that fit the level.
- Write the annotation by
goga-cookbookAnnotations writing standard (elements, theAlgorithm:placement
rule), references, and the sufficiency criterion: if not sufficient for implementation, add the missing element (Algorithm: / Requirements: / Constraints:).
- Verify against
goga-cookbookAnnotations — references resolve, no cross-level duplication, no implementation
details.
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.