create-skill

Stars10

Forks2

UpdatedMay 28, 2026 at 02:06

Converts an agentic prompt or Gemini Gem into a new structured skill for the Hypergraph Coding Agent Framework. Use this skill when asked to create a new skill from a prompt, gem, or idea.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

tjmustard

tjmustard/OIN-SMILES

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

File Explorer

3 files

SKILL.md

readonly

name	create-skill
description	Converts an agentic prompt or Gemini Gem into a new structured skill for the Hypergraph Coding Agent Framework. Use this skill when asked to create a new skill from a prompt, gem, or idea.

Create Skill

Follow these steps to predictably convert a Gemini Gem or generic agentic prompt into a properly formatted structural skill for the Hypergraph Coding Agent Framework.

When to use this skill

When the user provides an agentic prompt, a "Gemini Gem", or a raw textual description and asks you to create a "skill" out of it.
When the user runs the /hyper-create-skill slash command.

How to use it

Gather Inputs:
- Ensure you have the full content of the agentic prompt / Gemini Gem.
- Determine a short, hyphen-separated name for the skill (e.g., code-review or api-design).
- Determine a concise, third-person description of what the skill does (e.g., "Generates unit tests for Python code using pytest conventions.").
Create the Directory Structure:
- Create the primary skill folder at .agents/skills/<skill-name>/ (Workspace scope) or ~/.gemini/antigravity/skills/<skill-name>/ (Global scope). Default to workspace scope unless otherwise specified.
- Create the standard optional subdirectories:
  - scripts/ (for helper scripts)
  - examples/ (for reference implementations)
  - resources/ (for templates and assets)
Draft the SKILL.md File:
- Create the main instruction file at the root of the skill folder: SKILL.md.
- Mandatory Frontmatter: Start the file with the strict YAML frontmatter exactly as shown in this skill's resources/SKILL_TEMPLATE.md.
- Structure the Content: Adapt the prompt into the standard markdown format using the template as a guide. Ensure you include the ## When to use this skill and ## How to use it sections.
Organize and Create Auxiliary Files:
- Identify if the input prompt/Gem includes secondary materials (scripts, examples, JSON schemas, templates, etc.).
- Create any identified script files in the scripts/ subdirectory (ensure executable permissions if applicable).
- Create any identified example files in the examples/ subdirectory under the new skill.
- Create any identified template or asset files in the resources/ subdirectory under the new skill.
- Explicitly reference these auxiliary files from within the newly generated SKILL.md file using relative paths or explicit instructions.
Verify and Notify:
- Confirm the file is well-formed, valid YAML is used in the frontmatter, and all necessary directories and inputs have been written to disk.
- Read the examples provided in this skill's examples/ folder if you need a reference on how to format the new skill.
- Notify the user that the skill has been correctly scaffolded and the agent system can now dynamically discover it.

More from this repository

same repository

hyper-document

tjmustard/OIN-SMILES

Updates all project documentation after code or skill changes. Always reads actual implementation before writing. Covers README, CHANGELOG, docs/, AGENTS.md, memory files, and skills-info.md. Use after completing any feature, fix, refactor, or skill update.

2026-07-2710

handoff

tjmustard/OIN-SMILES

Compacts the current conversation into a handoff document so a fresh agent can continue the work. Saves to the OS temp directory, not the workspace. Pass an optional argument describing what the next session will focus on.

2026-07-2510

process-document

tjmustard/OIN-SMILES

Documents the process, methodology, and decisions of the current session as a reproducible narrative. Saves to spec/process/ in the workspace so the journey can be understood and recreated by others.

2026-07-2510

hyper-init

tjmustard/OIN-SMILES

Scaffolds a new project by conducting an interview to collect metadata and generating standard repository documentation files from the framework templates. Use when setting up a new repository.

2026-07-0310

hyper-tutorial-audit

tjmustard/OIN-SMILES

Run this after /hyper-tutorial-run to turn tutorial failures into a structured, constraint-aware goal prompt. Interviews the user about their goal and what may/may not be changed, then generates a paste-ready prompt for a new Claude Code fix session. Does NOT re-run tutorial commands.

2026-07-0310

tutorial-generator

tjmustard/OIN-SMILES

Generates a markdown tutorial from an integration test or user-provided files through iterative LLM + human collaboration. Tutorials are saved to tutorials/<name>/ with organized supporting files.

2026-07-0310

name	create-skill
description	Converts an agentic prompt or Gemini Gem into a new structured skill for the Hypergraph Coding Agent Framework. Use this skill when asked to create a new skill from a prompt, gem, or idea.

Create Skill

Follow these steps to predictably convert a Gemini Gem or generic agentic prompt into a properly formatted structural skill for the Hypergraph Coding Agent Framework.

When to use this skill

When the user provides an agentic prompt, a "Gemini Gem", or a raw textual description and asks you to create a "skill" out of it.
When the user runs the /hyper-create-skill slash command.

How to use it

Gather Inputs:
- Ensure you have the full content of the agentic prompt / Gemini Gem.
- Determine a short, hyphen-separated name for the skill (e.g., code-review or api-design).
- Determine a concise, third-person description of what the skill does (e.g., "Generates unit tests for Python code using pytest conventions.").
Create the Directory Structure:
- Create the primary skill folder at .agents/skills/<skill-name>/ (Workspace scope) or ~/.gemini/antigravity/skills/<skill-name>/ (Global scope). Default to workspace scope unless otherwise specified.
- Create the standard optional subdirectories:
  - scripts/ (for helper scripts)
  - examples/ (for reference implementations)
  - resources/ (for templates and assets)
Draft the SKILL.md File:
- Create the main instruction file at the root of the skill folder: SKILL.md.
- Mandatory Frontmatter: Start the file with the strict YAML frontmatter exactly as shown in this skill's resources/SKILL_TEMPLATE.md.
- Structure the Content: Adapt the prompt into the standard markdown format using the template as a guide. Ensure you include the ## When to use this skill and ## How to use it sections.
Organize and Create Auxiliary Files:
- Identify if the input prompt/Gem includes secondary materials (scripts, examples, JSON schemas, templates, etc.).
- Create any identified script files in the scripts/ subdirectory (ensure executable permissions if applicable).
- Create any identified example files in the examples/ subdirectory under the new skill.
- Create any identified template or asset files in the resources/ subdirectory under the new skill.
- Explicitly reference these auxiliary files from within the newly generated SKILL.md file using relative paths or explicit instructions.
Verify and Notify:
- Confirm the file is well-formed, valid YAML is used in the frontmatter, and all necessary directories and inputs have been written to disk.
- Read the examples provided in this skill's examples/ folder if you need a reference on how to format the new skill.
- Notify the user that the skill has been correctly scaffolded and the agent system can now dynamically discover it.