mirror of
https://github.com/sickn33/antigravity-awesome-skills.git
synced 2026-04-25 17:25:12 +02:00
42ce789b78
Adds two optional SKILL.md frontmatter fields for downstream consumers (e.g. aggregators and MCP servers) that need to resolve the license of upstream-sourced skills at ingest time. - `license`: SPDX expression for the upstream source material (e.g. `MIT`) - `license_source`: URL to the upstream LICENSE file for automated verification Both fields are strictly optional and non-breaking. Existing skills with no `license` field are treated as "license not declared" by tooling — no inference or default is assumed. Also adds: - PR checklist item prompting contributors to declare license provenance when `source_repo` is set (`.github/PULL_REQUEST_TEMPLATE.md`) - "License provenance" subsection in `docs/contributors/skill-anatomy.md` documenting when and how to use the new fields Co-authored-by: Joel Morrison <spinbitz@gmail.com> Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2.3 KiB
2.3 KiB
Pull Request Description
Please include a summary of the change and which skill is added or fixed.
Change Classification
- Skill PR
- Docs PR
- Infra PR
Issue Link (Optional)
Use this only when the PR should auto-close an issue:
Closes #N or Fixes #N
Quality Bar Checklist ✅
All applicable items must be checked before merging.
- Standards: I have read
docs/contributors/quality-bar.mdanddocs/contributors/security-guardrails.md. - Metadata: The
SKILL.mdfrontmatter is valid (checked withnpm run validate). - Risk Label: I have assigned the correct
risk:tag (none,safe,critical,offensive, orunknownfor legacy/unclassified content). - Triggers: The "When to use" section is clear and specific.
- Limitations: The skill includes a
## Limitations(or equivalent accepted constraints) section. - Security: If this is an offensive skill, I included the "Authorized Use Only" disclaimer.
- Safety scan: If this PR adds or modifies
SKILL.mdcommand guidance, remote/network examples, or token-like strings, I rannpm run security:docs(or equivalent hardening check) and addressed any findings. - Automated Skill Review: If this PR changes
SKILL.md, I checked theskill-reviewGitHub Actions result and addressed any actionable feedback. - Manual Logic Review: If this PR changes
SKILL.mdor risky guidance, I manually reviewed the logic, safety, failure modes, andrisk:label instead of relying on automated checks alone. - Local Test: I have verified the skill works locally.
- Repo Checks: I ran
npm run validate:referencesif my change affected docs, workflows, or infrastructure. - Source-Only PR: I did not manually include generated registry artifacts (
CATALOG.md,skills_index.json,data/*.json) in this PR. - Credits: I have added the source credit in
README.md(if applicable). - License provenance: If this skill imports from an external
source_repo, I have declaredlicense:andlicense_source:in the frontmatter, or confirmed the upstream repo carries no restricting license. - Maintainer Edits: I enabled Allow edits from maintainers on the PR.