skill-contribution-assistant

Guide contributors to create PR-ready AL Copilot skills with compliant SKILL.md artifacts.

99|28|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/javiarmesto/ALDC-AL-Development-Collection --skill skill-contribution-assistant-javiarmesto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-contribution-assistant
Source: https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/claude-plugin/skills/skill-contribution-assistant
Command: npx skills add https://github.com/javiarmesto/ALDC-AL-Development-Collection --skill skill-contribution-assistant-javiarmesto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps contributors move from idea to PR-ready skill with consistent quality standards by providing a structured playbook.

Core Features & Use Cases

  • Onboarding guidance for new community skills, including mandatory questions and guardrails.
  • Governance and release planning steps to ensure skills are proposed, approved, and merged with proper documentation.
  • File structure and frontmatter guidance to keep SKILL.md compact and maintainable, with long content moved to references.
  • Non-intrusive evaluation workflow to detect reusable skill opportunities without disrupting user tasks.

Quick Start

Begin by framing the skill scope and preparing the initial SKILL.md following the playbook.

Frequently Asked Questions about skill-contribution-assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a PR-ready AL Copilot skill for community contribution?

To create a PR-ready AL Copilot skill, frame the scope and prepare an initial SKILL.md following a structured playbook that ensures correct file layout, metadata, and documentation references for governance compliance.

What is the correct file structure and frontmatter for an AL Copilot skill?

The correct file structure keeps SKILL.md compact and maintainable by moving long content to references, while frontmatter must include accurate metadata to satisfy governance, maintainability, and PR-readiness requirements.

How do I ensure my community skill proposal meets governance and release planning requirements?

Community skill proposals meet governance and release planning requirements by completing mandatory onboarding questions, integrating release-plan steps, and delivering compliant governance artifacts alongside the SKILL.md file.

Can I evaluate reusable skill opportunities without disrupting my current user tasks?

Yes, you can evaluate reusable skill opportunities without disrupting user tasks by applying a non-intrusive evaluation workflow that detects potential skills during normal operations.

Do I need any specific dependencies or tools to draft a compliant AL Copilot skill?

No specific external dependencies are required to draft a compliant AL Copilot skill; the process focuses on applying provided templates, onboarding guidance, and governance artifacts directly to your skill proposal.

When should I move content from SKILL.md into separate reference files?

You should move long content from SKILL.md into separate reference files when the main skill documentation exceeds compact maintainability limits, ensuring the primary file remains readable and compliant.