AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified BSD-3-Clause Self-run

Goga Brainstorm Contracts Usages File

skill-qarium-goga-goga-brainstorm-contracts-usages-file · by qarium

Designing cell-level consumer usage files for a single cell in the brainstorm contracts pipeline

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-qarium-goga-goga-brainstorm-contracts-usages-file

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-qarium-goga-goga-brainstorm-contracts-usages-file)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Goga Brainstorm Contracts Usages File? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

goga-brainstorm-contracts-usages-file

Algorithm

Design the consumer API documentation in /.usages/ for the given cell.

  • The rules for writing /.usages/ files follow goga-cookbook.
  • .usages/ placement and {name}.md path resolution follow goga-cell.

Step 1 — Collect the cell's API

Build the factual basis for the documentation:

  • From [TYPE_DETAIL_REPORT] — the cell's contract: each type's responsibility, methods/properties/signatures, and

interactions. This is the API surface a consumer calls.

  • From the usages-inline and annotations results — the connected Usages keys and the documented behavior, so the

examples reflect how the cell is meant to be consumed.

Step 2 — Review existing usage files

Review existing md files in /.usages/ — preserve or extend them; do not overwrite blindly.

Step 3 — Split into functional domains

Split the API (Step 1) into functional domains by the actions a consumer performs.

Step 4 — One file per domain

One file per domain: /.usages/.md.

Step 5 — Write the content

Per file: a domain statement (area + target audience), ready-to-use patterns with code examples, and preconditions/side effects relevant to the consumer. Self-contained — describes how to use, not what to implement.

Return

Return the paths: /.usages/.md and Full usage-files content.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.