aget-create-skill

Create new AGET skills with standardized templates and S-V-O naming.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to scaffold new AGET skills using standardized templates, ensuring consistent vocabulary, specs, and traceability across artifacts.

Core Features & Use Cases

  • Enforces S-V-O naming conventions for new skills.
  • Automates creation of SKILL.md with valid frontmatter and linked specifications.
  • Updates the skills index and preserves full traceability from specs to implementation.

Quick Start

Provide a valid /aget- style skill name to begin the creation process.

Frequently Asked Questions about aget-create-skill

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

FAQPage Schema
How do I create a new AGET skill using standard templates?

To create a new AGET skill, provide a valid /aget-* style skill name. The tool then scaffolds the skill by enforcing S-V-O naming conventions, generating a SKILL.md file with valid frontmatter, and creating linked specifications.

What are S-V-O naming conventions for skill creation?

S-V-O naming conventions standardize skill names using a Subject-Verb-Object structure. Enforcing this format ensures consistent vocabulary and clear intent across newly scaffolded AGET skills and their design specifications.

How do I maintain traceability across skill specifications and implementation artifacts?

You maintain traceability by using templates that automatically generate SKILL.md with linked specifications and update the skills index. This process preserves full traceability from specs to implementation artifacts.

Do I need to manually update the skills index when scaffolding a new skill?

No, you do not need to manually update the skills index. The skill creation process automatically updates the index while generating the necessary specification and traceability artifacts.

What is the best way to scaffold a skill with valid frontmatter?

The best way to scaffold a skill with valid frontmatter is to use a standardized template generator. This automatically creates the SKILL.md file and enforces required metadata fields during the /aget-* skill creation process.