licencing — for Claude Code licencing, map2-audio, community, for Claude Code, ide skills, AGPL-3.0-only, repeatable, compliance, repository, declared

v1.0.0

À propos de ce Skill

Scenario recommande : Ideal for AI agents that need apply a repeatable compliance workflow for this repository's declared policy:. Resume localise : Third-party dependencies and vendored components keep their original licenses. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Fonctionnalités

Apply a repeatable compliance workflow for this repository's declared policy:
Third-party dependencies and vendored components keep their original licenses.
Educational statements in docs are intent statements and must not add restrictions beyond AGPLv3.
Treat this skill as an engineering compliance workflow, not legal advice.
Compliance Workflow

# Core Topics

matthewmackes matthewmackes
[3]
[0]
Updated: 4/30/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
49
Canonical Locale
en
Detected Body Locale
en

Scenario recommande : Ideal for AI agents that need apply a repeatable compliance workflow for this repository's declared policy:. Resume localise : Third-party dependencies and vendored components keep their original licenses. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Pourquoi utiliser cette compétence

Recommandation : licencing helps agents apply a repeatable compliance workflow for this repository's declared policy:. Third-party dependencies and vendored components keep their original licenses. This AI agent skill

Meilleur pour

Scenario recommande : Ideal for AI agents that need apply a repeatable compliance workflow for this repository's declared policy:.

Cas d'utilisation exploitables for licencing

Cas d'usage : Applying Apply a repeatable compliance workflow for this repository's declared policy:
Cas d'usage : Applying Third-party dependencies and vendored components keep their original licenses
Cas d'usage : Applying Educational statements in docs are intent statements and must not add restrictions beyond AGPLv3

! Sécurité et Limitations

  • Limitation : Educational statements in docs are intent statements and must not add restrictions beyond AGPLv3.
  • Limitation : Educational statements in docs are intent statements and must not add restrictions beyond AGPLv3
  • Limitation : Requires repository-specific context from the skill documentation

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is licencing?

Scenario recommande : Ideal for AI agents that need apply a repeatable compliance workflow for this repository's declared policy:. Resume localise : Third-party dependencies and vendored components keep their original licenses. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install licencing?

Run the command: npx killer-skills add matthewmackes/map2-audio/licencing. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for licencing?

Key use cases include: Cas d'usage : Applying Apply a repeatable compliance workflow for this repository's declared policy:, Cas d'usage : Applying Third-party dependencies and vendored components keep their original licenses, Cas d'usage : Applying Educational statements in docs are intent statements and must not add restrictions beyond AGPLv3.

Which IDEs are compatible with licencing?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for licencing?

Limitation : Educational statements in docs are intent statements and must not add restrictions beyond AGPLv3.. Limitation : Educational statements in docs are intent statements and must not add restrictions beyond AGPLv3. Limitation : Requires repository-specific context from the skill documentation.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add matthewmackes/map2-audio/licencing. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use licencing immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

licencing

Third-party dependencies and vendored components keep their original licenses. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows. Apply

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Licencing

Apply a repeatable compliance workflow for this repository's declared policy:

  • All MAP2-owned code and project artifacts are AGPLv3 (AGPL-3.0-only) unless a file/package explicitly declares a different license.
  • Third-party dependencies and vendored components keep their original licenses.
  • Educational statements in docs are intent statements and must not add restrictions beyond AGPLv3.

Treat this skill as an engineering compliance workflow, not legal advice.

Compliance Workflow

  1. Identify scope of changed or audited code.
  2. Classify each area as MAP2-owned AGPL, third-party license override, or ambiguous ownership.
  3. Run checklist in references/licensing-compliance-checklist.md.
  4. Record concrete gaps with file paths and evidence.
  5. Add or update tasks in docs/PROJECT_WORKLIST.md for every unresolved gap.
  6. Re-run checks after edits and mark tasks accordingly.

Scope Classification

Use fast repository scans:

bash
1rg -n "license|LICENSE|AGPL|GNU Affero|THIRD_PARTY_NOTICES|SPDX" README.md LICENSE docs .codex/skills/licencing 2rg --files -g "LICENSE*" -g "*COPYING*" -g "*NOTICE*"

Classify with these rules:

  • MAP2-owned AGPL scope:
    • Repository code/docs/configuration authored for MAP2 unless explicitly overridden.
  • Third-party override scope:
    • vendored modules/packages with their own license files.
  • Ambiguous scope:
    • unknown ownership/provenance that cannot be verified from file history and notices.

If classification is ambiguous, mark as a compliance question and create a worklist task.

Required Outputs

Produce:

  • Brief compliance status summary:
    • pass/fail per checklist section
    • unresolved gaps with file references
  • Worklist updates in docs/PROJECT_WORKLIST.md for unresolved items.
  • Exact commands and evidence used for the audit.

Worklist Rules

When a gap exists, add a task immediately:

  • Use canonical file: docs/PROJECT_WORKLIST.md.
  • Follow repository task schema exactly (ID, Status, Title, Description, Dependencies, Effort, Required outputs, Last updated).
  • Use the next available top-level T### ID.
  • Add subtasks when the remediation has multiple independent deliverables.
  • Update the worklist header timestamp whenever tasks are added/changed.

Use the templates and gap-to-task mapping in references/licensing-compliance-checklist.md.

Compétences associées

Looking for an alternative to licencing or another community skill for your workflow? Explore these related open-source skills.

Voir tout

openclaw-release-maintainer

Logo of openclaw
openclaw

Resume localise : 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

widget-generator

Logo of f
f

Resume localise : Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

flags

Logo of vercel
vercel

Resume localise : The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

138.4k
0
Navigateur

pr-review

Logo of pytorch
pytorch

Resume localise : Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

98.6k
0
Développeur