skill-architect

Design and document validated SKILL.md files for Gemini CLI.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/MGriot/.gemini --skill skill-architect-mgriot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-architect
Source: https://github.com/MGriot/.gemini/tree/main/skills/skill-architect
Command: npx skills add https://github.com/MGriot/.gemini --skill skill-architect-mgriot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill Architect provides a structured approach to designing and documenting Agent Skills for the Gemini CLI. It ensures every Skill has a clear frontmatter foundation (name and description) and a well-organized body that can be used directly by the agent.

Core Features & Use Cases

  • Structured SKILL.md templates: Enforces a consistent frontmatter and body structure to speed up Skill creation.
  • TDD-guided workflow: Uses a test-driven mindset to validate Skill content before deployment.
  • Metadata discipline: Advocates for kebab-case names, precise descriptions, and actionable triggers.
  • Documentation-to-Action bridge: Transforms prose into deterministic steps, ready for activation in Gemini CLI.

Quick Start

Create or update a Skill directory by adding a SKILL.md with proper frontmatter, then draft the body with a clear stepwise workflow.

Frequently Asked Questions about skill-architect

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

FAQPage Schema
How do I structure a SKILL.md file for Gemini CLI?

To structure a SKILL.md file for Gemini CLI, include YAML frontmatter with name and description fields, followed by a stepwise workflow body and optional resource directories for scripts and references.

What is the best way to document agent workflows for Gemini CLI?

Documenting agent workflows requires transforming prose into deterministic stepwise actions within a SKILL.md file, ensuring clear metadata discipline with kebab-case names and actionable triggers for agent activation.

How does test-driven development apply to creating Gemini Skills?

Test-driven development for Gemini Skills validates the SKILL.md content and stepwise workflow before deployment, ensuring the structured frontmatter and deterministic steps function correctly for the agent.

Do I need YAML frontmatter to create a Skill for Gemini CLI?

Yes, YAML frontmatter is required to create a Skill for Gemini CLI, specifically enforcing the inclusion of name and description fields to establish a clear foundation for agent capabilities.

Can I include automation scripts in my Gemini CLI Skill package?

Yes, you can include automation scripts in your Gemini CLI Skill package by utilizing optional resource directories, which also support references and assets for comprehensive workflow automation.

What are the limitations of using templates for Agent Skill design?

Templates for Agent Skill design enforce strict structural consistency, which may limit freeform documentation styles but guarantees robust frontmatter foundations and predictable agent activation.