aget-propose-skill

Create structured Markdown skill proposals with validation and governance checks.

1|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-propose-skill-gmelli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aget-propose-skill
Source: https://github.com/gmelli/public-OpenAI-DeepResearch-aget/tree/main/.claude/skills/aget-propose-skill
Command: npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-propose-skill-gmelli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents unreviewed and ad hoc skill creation by requiring a structured proposal process that captures purpose, triggers, scope, and dependencies before implementation, reducing duplication and governance gaps.

Core Features & Use Cases

  • Structured Proposal Generation: Collects skill name, purpose, triggers, category, and scope and generates a standardized Markdown proposal artifact.
  • Validation & Safeguards: Enforces name pattern aget-{verb}-{object}, checks for uniqueness against existing skills, and requires a minimum of two triggers before proceeding.
  • Governance Workflow: Produces a proposal file in planning/skill-proposals/ for review, supports index updating, and provides clear next steps to review and implement approved skills.
  • Use Case: A product manager uses the skill to formalize a new capability request, ensuring reviewability and traceability before engineering investment.

Quick Start

Propose a new skill named aget-record-lesson with purpose record lessons learned, include triggers record lesson and note lesson, set category Governance and scope Universal.

Frequently Asked Questions about aget-propose-skill

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

FAQPage Schema
How do I formalize a proposal for a new agent skill?

To formalize a proposal for a new agent skill, you use a structured governance workflow that captures purpose, triggers, scope, and dependencies, generating a standardized Markdown artifact for pre-implementation review.

What validation rules apply to skill naming and triggers during workflow planning?

Validation rules for workflow planning require the skill name to match the aget-{verb}-{object} pattern, verify uniqueness against the skills directory, and mandate at least two triggers before generating the proposal.

Why do I need a structured proposal process for agent development?

You need a structured proposal process for agent development to prevent unreviewed ad hoc skill creation, reducing duplication and governance gaps by ensuring traceability before engineering investment.

Can I use this governance workflow for both universal and agent-specific scopes?

Yes, you can apply this governance workflow to pre-implementation review and planning across both universal and agent-specific scopes, outputting a reviewable Markdown file to the planning directory.

How do I generate a standardized proposal artifact for agent management?

To generate a standardized proposal artifact for agent management, input the skill name, purpose, triggers, category, and scope, creating a Markdown file at planning/skill-proposals/PROPOSAL_{name}.md.