gsd-quick

Identify valid Skill units by locating SKILL.md files and verifying YAML frontmatter.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-quick-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-quick
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-quick-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you complete small, ad hoc work with GSD guarantees while keeping execution atomic, tracked, and resumable.

Core Features & Use Cases

  • Quick task execution for one-off changes that should still be recorded cleanly in state files.
  • Optional discussion, research, validation, and resume flows for tasks that need more control.
  • Useful for operational work such as triaging a request, resuming an interrupted task, or listing existing quick tasks.

Quick Start

Invoke the gsd-quick skill with a short task description or a resume command so it can load the right quick-workflow context and continue safely.

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I locate valid Skill units in a repository by scanning for SKILL.md files?

To locate valid Skill units in a repository, scan directory trees for root SKILL.md files. A directory qualifies as a valid skill unit only if this entry point exists, contains YAML frontmatter, and includes a name and description.

How do I extract metadata and operational scope from YAML frontmatter in a skill directory?

You can extract metadata and operational scope from YAML frontmatter by verifying its presence within the root SKILL.md file. This process identifies the skill's configuration details and runtime context within the repository.

What is the best way to run quick ad hoc tasks with safe state tracking and atomic execution?

Running quick ad hoc tasks with safe state tracking requires a workflow that keeps execution atomic, tracked, and resumable. This ensures small changes are recorded cleanly in state files without losing progress on interruptions.

Can I resume an interrupted task or triage a request using a quick workflow context?

Yes, you can resume an interrupted task or triage a request by invoking the quick workflow context with a resume command. This loads the prior state safely, allowing operational work to continue without losing tracked progress.

Does a directory need optional scripts and references to qualify as a valid skill unit?

No, a directory does not need optional scripts, references, or assets to qualify as a valid skill unit. The only strict requirement is the presence of a named and described SKILL.md entry point with valid YAML frontmatter.

When do I need to verify YAML frontmatter during repository analysis for skill discovery?

You need to verify YAML frontmatter during repository analysis when identifying valid skill units. This verification confirms the SKILL.md file contains the required metadata structure to properly extract operational scope and runtime context.