goga-accept-scope SKILL.md skillA
goga-accept-scope from qarium/goga is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qarium/goga/goga-accept-scope@git:20260629.9657abaPins git:20260629.9657aba in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qarium/goga
- Path
goga/assets/skills/goga-accept-scope/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260629.9657aba, committed Jun 29, 2026
- Size
- 2,299 bytes
- Repository stars
- 44
- License
- BSD-3-Clause
Defines the acceptance scope — the set of cells for a given functionality.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# goga-accept-scope
## Identity
You are responsible for defining the acceptance scope — identifying the set of cells associated with a given functionality.
## Algorithm
### Determine acceptance scope
Acceptance operates at the functionality level. One functionality may span one or more cells.
Resolve the scope:
1. **Arguments contain a functionality description or path** — use as `<target>`
2. **Arguments are empty** — analyze `git diff` to identify changed files
3. **No changes found or scope is ambiguous** — prompt the user via AskUserQuestion:
- **question**: "Which functionality should undergo acceptance?"
- **header**: "Acceptance scope"
- **multiSelect**: false
- **options**:
- **label**: "Branch changes", **description**: "Determine from git diff"
- **label**: "Specific functionality", **description**: "Provide a functionality description"
- **label**: "All project cells", **description**: "Full acceptance"
### Map scope to cells
1. Load the project schema: `goga schema`
2. Match the functionality description or `git diff` results to cells in the schema
3. For each matched cell:
a. Verify the CODEMANIFEST file exists
…Read the whole file at its exact version.
How to install
mdr add qarium/goga/goga-accept-scope@sha256:09f14a6915f36a03The line at the top of this page pins the label git:20260629.9657aba, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pasvstz7p3fawc3v)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 29, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2299 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qarium/goga · 44 stars · license BSD-3-Clause · pushed 2026-10-21 · branch 2.1.x
API
GET https://markdownregistry.com/api/v1/artifacts/art_pasvstz7p3fawc3v GET https://markdownregistry.com/api/v1/resolve?ref=qarium/goga/goga-accept-scope GET https://markdownregistry.com/api/v1/blob/09f14a6915f36a03120f294bcaa12b008cb260b40b825fede94c01837af235b2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.