drevendev/HungryCrab / skills/license
license
VerifiedDecide what may be carried over from a prey repository under its license. Modes are COPY, COPY_FILE, REIMPLEMENT, IDEAS_ONLY and HUMAN. Use when a nutrient's license mode is unclear, when asked whether code or configs from another repository may be copied, or when a sniff verdict says HUMAN. Do not use to choose the maw's own license, for general legal advice, or for licensing questions unrelated to prey-to-maw transfer.
License rules
The verdict is produced by a deterministic engine (crab sniff, license.json in a digest).
Your job is to apply the mode, explain it, and stop when the engine says HUMAN.
The repository overview and an established selected-path verdict have separate scope.
discover packet exposes immutable path grants; explore register and serve share the resolver.
An equivalent nested grant, a notice-only COPYRIGHT or a separate licence specimen need not
relicense unrelated implementation files. The CLI retains actual grants and all applicable notices.
Use its established result, never a hand-edited mode. Unknown components, missing notices,
conflicting grants and unsupported references stay held; MIT-only applies to the selected material.
Modes
| Mode | Allowed | Required |
|---|---|---|
COPY | copy code, configs and text | keep the copyright notice; publish through crab serve --as pr-branch with a materialization receipt (the serve skill), which records the source in .crab/attributions.json and renders THIRD_PARTY_NOTICES.md; Apache-2.0 also needs the NOTICE file's attribution notices carried over |
COPY_FILE | copy whole files (MPL-2.0, EPL, CC-BY-SA documents) | the file keeps its own license header; do not merge it into files under the maw license; every file in the receipt is verbatim |
REIMPLEMENT | use the prey as a specification | clean room: a spec without code, then the crab-cleanroom-impl subagent without prey-cache access; record "implemented from a specification" in the trace |
IDEAS_ONLY | ideas, architecture, approaches, facts | not a line of code, configuration or documentation text |
HUMAN | nothing yet | a person decides; present the evidence (license.json: files, manifests, headers, conflicts) |
Rules that override the matrix
- Issue, discussion and pull-request comment text is always
IDEAS_ONLY: the copyright belongs to the commenters. Carry over the need and a link, not the text. The CLI enforces this from content origin, records the origin and cap reason in the nutrient trace, andcrab servecarries that trace into the served issue; do not recalculate the cap by hand. The cap rewrites the card's title andwhat; yourwhyandhoware yours to keep clean, andcrab serverefuses a card of any origin butlicensedwhose notes quote one of the prey's issue titles, in any punctuation or case, or whose notes cannot be checked. - Configuration files and small snippets are not automatically free: same mode as code.
- Strict mode is enforced by the CLI.
.crab.ymlmode: strictdowngradesCOPYcode to clean-roomREIMPLEMENT; configs and templates stay copyable.menu.jsonrecords the material, maw mode and policy reason, and served issues carry the reason in their license trace. Use that verdict and the clean-room protocol; do not calculate or reverse the downgrade by hand. - Per-file exceptions in
license.json(vendored directories, headers with another SPDX id) override the repository license for those files. - No license at all is
IDEAS_ONLYwith human review, notHUMAN.HUMANis only for a license that was read and could not be classified. The two ask for different things: underIDEAS_ONLYthe need and the facts may still travel, underHUMANnothing may until a person answers. - Review is a flag, not a mode. A conflict between the LICENSE file and a manifest does not
change the verdict — the mode still comes from the detected license, and the digest records
the conflict in
license.jsonunderconflictswithhuman_review: truebeside it. Read both:human_reviewis also true for a source-available license, whose mode isIDEAS_ONLY.
How to compute a mode
crab sniff <prey> --maw .prints the mode for this maw.license.jsonin the prey digest hasmodes_by_maw_class(permissive, gpl, proprietary maws) andverdictwhen a maw license was known at digest time.mode_maw_samplesnames the representatives:gplis GPL-3.0-only, not the whole GPL family. Use the actual maw's verdict for adoption decisions.- The full matrix is in
references/matrix.md.
This is a compliance aid, not legal advice; say so when the user asks about an edge case.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |