avadbeta-help

List shipped and planned native avad skills from frontmatter metadata.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/agwacom/avadbeta --skill avadbeta-help
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: avadbeta-help
Source: https://github.com/agwacom/avadbeta/tree/main/codex-plugin/skills/avadbeta-help
Command: npx skills add https://github.com/agwacom/avadbeta --skill avadbeta-help

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lists native avad skills and show shipped-vs-planned.

Core Features & Use Cases

  • Enumerates shipped native skills and their status (shipped vs planned).
  • Provides quick visibility into which skills are available now and which are planned.

Quick Start

Ask /avadbeta-help to list shipped and planned avad skills.

Frequently Asked Questions about avadbeta-help

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

FAQPage Schema
How do I list all available skills and see which ones are shipped vs planned?

To list available skills and see shipped vs planned statuses, invoke the help command to enumerate native capabilities. It reads frontmatter metadata and the current skill surface to display which features are ready for use now and which are still in the planning phase.

What is the best way to discover what the avad platform can do?

Discovering what the avad platform can do is done by querying the skill surface for a full enumeration of native capabilities. This provides quick visibility into available features, allowing you to understand the platform's current scope and planned roadmap at a single glance.

How do I get started with finding native skills for my workflow?

Getting started with finding native skills requires asking for a discovery list of shipped and planned capabilities. The system applies frontmatter metadata to enumerate available features, giving you a clear status overview to identify the right tools for your workflow immediately.

Can I check the development status of planned capabilities before building a workflow?

Checking the development status of planned capabilities before building a workflow is fully supported. The enumeration feature relies on frontmatter metadata to distinguish between shipped skills ready for deployment and planned skills still under development, preventing reliance on unavailable features.

Does the skill discovery process require any external dependencies or components?

The skill discovery process requires no external dependencies or components to function. It operates natively by reading existing frontmatter metadata and the current skill surface, allowing you to enumerate shipped and planned capabilities without any additional environment setup or installation.

Why does a planned skill show up in my discovery list if it is not available yet?

A planned skill shows up in your discovery list because the enumeration mechanism reads frontmatter metadata to provide complete roadmap visibility. It intentionally displays both shipped native skills and planned capabilities side by side, ensuring you know exactly what features are currently unavailable but scheduled.