New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Output Dev Skill File

by growthxai in growthxai/output

Create .md skill files for Output framework's lazy-loaded instruction system.

Apache-2.0Auto-check passedDevelopment

Install Output Dev Skill File

skills CLI
$ npx skills add growthxai/output --skill output-dev-skill-file -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install growthxai/output output-dev-skill-file --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/growthxai/output.git skills-src && mkdir -p .claude/skills && cp -r skills-src/coding_assistants/claude/plugins/outputai/skills/output-dev-skill-file .claude/skills/output-dev-skill-file && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
output-dev-skill-file
GitHub stars
442
Token cost
~2.1k tokens
SKILL.md length
571 words
Files
1
Skills in repo
52
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create .md skill files for Output framework's lazy-loaded instruction system.

  • Works in 4 steps: Write Focused Skills → Write Descriptive Descriptions → Structure Instructions with Headers → …
  • Adding skills to prompts
  • SKILL.md covers Overview, When to Use This Skill, Location Convention and Skill File Format, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Output Dev Skill File is an agent skill from growthxai/output. Create .md skill files for Output framework's lazy-loaded instruction system. Use when adding skills to prompts, configuring skill loading, or debugging skill resolution.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: The open-source TypeScript framework for building AI workflows and agents. Designed for Claude Code describe what you want, Claude builds it, with all the best practices already… The licence is Apache-2.0.

When your agent uses it

  • Adding skills to prompts
  • Configuring skill loading
  • Debugging skill resolution

Example prompts

  • “/output-dev-skill-file”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Write Focused Skills
  2. Write Descriptive Descriptions
  3. Structure Instructions with Headers
  4. Include Actionable Guidance

What it can do on your machine

Read from SKILL.md and the folder at commit ff9e1ab. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown, yaml and typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Output Dev Skill File loads about 2.1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 571 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from growthxai/output at commit ff9e1ab, republished under its Apache-2.0 licence (© growthxai). 571 words, ~2,129 tokens.

Download SKILL.mdSave it as .claude/skills/output-dev-skill-file/SKILL.md (or your agent's skills folder).
name
output-dev-skill-file
description
Create .md skill files for Output framework's lazy-loaded instruction system. Use when adding skills to prompts, configuring skill loading, or debugging skill resolution.
allowed-tools
Read, Write, Edit

Creating Skill Files

Overview

This skill documents how to create .md skill files for the Output framework's skills system. Skills are lazy-loaded instruction packages that keep prompts lightweight. The LLM sees a list of skill names and descriptions in the system message, then calls a load_skill tool to retrieve full instructions on demand.

Important: These are framework skills (.md files loaded by LLMs at runtime), not Claude Code plugin skills. The naming is similar but the systems are separate.

When to Use This Skill

  • Adding reusable instruction sets to LLM prompts
  • Listing skill paths in prompt frontmatter
  • Debugging skill resolution or load_skill tool issues
  • Organizing shared expertise across multiple prompts

Location Convention

Skill files live in a skills/ folder next to the prompt file. List that folder (or individual files) in the prompt frontmatter. A sibling skills/ directory is not loaded unless the prompt names it:

src/workflows/{workflow-name}/
├── workflow.ts
├── steps.ts
├── types.ts
└── prompts/
    ├── writing_assistant@v1.prompt
    └── skills/
        ├── clarity_guidelines.md
        ├── response_format.md
        └── structure_guide.md

The skills/ folder is relative to the prompt file location, not the workflow root.

Skill File Format

Skill files are markdown documents with an optional YAML frontmatter block:

markdown
---
name: clarity_guidelines
description: Rules for writing clear, readable technical content
---

# Clarity Guidelines

When reviewing or writing technical content for clarity:

1. **Sentence length**: Keep sentences under 25 words when possible.
   Break complex ideas into multiple sentences.

2. **Active voice**: Prefer active voice ("The function returns X")
   over passive ("X is returned by the function").

3. **Jargon**: Define technical terms on first use.
   Avoid unnecessary acronyms without explanation.

4. **Concrete examples**: Every abstract concept should have
   a concrete example.

When applying this skill, flag any violations you find
and suggest improvements.
Frontmatter Fields
FieldRequiredDefaultDescription
nameNoFilename without .mdIdentifier the LLM uses with load_skill
descriptionNoSame as nameShown in system message, helps LLM decide when to load
BodyYes-Full instructions returned when LLM calls load_skill

If you omit the frontmatter entirely, the filename (without .md) is used as both the name and description. A file named clarity_guidelines.md with no frontmatter gets name: "clarity_guidelines" and description: "clarity_guidelines".

Write good descriptions. They appear in the system message and are what the LLM uses to decide whether to load a skill. "Rules for writing clear, readable technical content" is better than "clarity_guidelines".

How Skills Are Loaded

List skill paths in the prompt YAML frontmatter. Paths resolve relative to the prompt file and can be individual .md files or directories of .md files. (Model lines below are current as of 2026-05-04 - refresh via output-dev-model-selection.)

yaml
---
provider: anthropic
model: claude-sonnet-4-6
maxOutputTokens: 2048
skills:
  - ./skills
  - ../shared_skills/tone_guide.md
---

<system>
You are an expert technical writing assistant.
Use load_skill to get full instructions for any skill before applying it.
</system>

<user>
Review the following {{ content_type }} content focusing on {{ focus }}.

Content:
{{ content }}
</user>

At runtime, Output loads the listed paths and:

  1. Adds a summary of available skills to the system message
  2. Injects a load_skill tool the LLM can call

List skill paths in the prompt frontmatter.

Omit skills (or set skills: []) when a prompt should load none. A sibling skills/ folder used by other prompts in the same directory is not inherited.

Show full SKILL.md (190 more words)Show less

Complete Example

Skill File
markdown
---
name: response_format
description: Standard format requirements for all review responses
---

# Response Format

Every response MUST end with the exact string "OUTPUT_COMPLETE" on its own line.

Structure your review as follows:

1. **Summary**: 2-3 sentence overview of the content quality
2. **Issues**: Numbered list of specific problems found
3. **Suggestions**: Actionable improvements for each issue
4. **Score**: Overall quality score from 0-100

OUTPUT_COMPLETE
Prompt File Using Skills
yaml
---
provider: anthropic
# current as of 2026-05-04 - run output-dev-model-selection for the latest
model: claude-sonnet-4-6
maxOutputTokens: 2048
skills:
  - ./skills
---

<system>
You are an expert technical writing assistant.
Use load_skill to get the full instructions for any skill before applying it.
After reviewing, provide structured feedback with specific issues and suggestions.
</system>

<user>
Review the following {{ content_type }} content focusing on {{ focus }}.

Content:
{{ content }}
</user>
Step Using the Prompt
typescript
import { step, z } from '@outputai/core';
import { Agent, aiSdk } from '@outputai/llm';

export const reviewContent = step( {
  name: 'reviewContent',
  description: 'Review content using skills for specialized expertise',
  inputSchema: z.object( {
    content: z.string(),
    content_type: z.string(),
    focus: z.string()
  } ),
  outputSchema: z.object( {
    summary: z.string(),
    issues: z.array( z.string() ),
    suggestions: z.array( z.string() ),
    score: z.number()
  } ),
  fn: async input => {
    const agent = new Agent( {
      prompt: 'writing_assistant@v1',
      variables: input,
      output: aiSdk.Output.object( {
        schema: z.object( {
          summary: z.string().describe( '2-3 sentence overview' ),
          issues: z.array( z.string() ).describe( 'Specific problems found' ),
          suggestions: z.array( z.string() ).describe( 'Actionable improvements' ),
          score: z.number().describe( 'Quality score 0-100' )
        } )
      } )
    } );
    const { output } = await agent.generate();
    return output;
  }
} );

Best Practices

1. Write Focused Skills

Each skill should cover one area of expertise. Prefer multiple focused skills over one large skill:

skills/
├── clarity_guidelines.md      # Writing clarity
├── structure_guide.md         # Document structure
└── response_format.md         # Output formatting
2. Write Descriptive Descriptions

The description appears in the system message. Make it clear when the LLM should load this skill:

yaml
---
name: clarity_guidelines
description: Rules for writing clear, readable technical content
---

Not:

yaml
---
name: clarity_guidelines
description: clarity_guidelines
---
3. Structure Instructions with Headers

Use markdown headers and lists for scannable instructions:

markdown
# Clarity Guidelines

## Rules
1. Keep sentences under 25 words
2. Prefer active voice
3. Define jargon on first use

## When to Flag
- Sentences over 30 words
- Passive voice in instructions
- Undefined acronyms
4. Include Actionable Guidance

Tell the LLM what to do with the skill, not just what the skill is about:

markdown
When applying this skill, flag any violations you find and suggest improvements.

Verification Checklist

  • Prompt frontmatter lists skill paths (skills: ./skills or explicit files)
  • Each skill has a clear, descriptive description in frontmatter
  • Skill body contains actionable instructions
  • Prompt file mentions load_skill in the system message
  • Listed paths resolve relative to the prompt file
  • Prompts that should load no skills omit skills (or set skills: [])
  • Skills are focused (one area of expertise per file)
  • Prompt frontmatter sets maxSteps when the tool-loop ceiling should not be 10
  • output-dev-prompt-file - Creating .prompt files that use skills
  • output-dev-agent-class - Using the Agent class with skills
  • output-dev-step-function - Using skills in step functions
  • output-dev-folder-structure - Understanding skill file locations

© growthxai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in coding_assistants/claude/plugins/outputai/skills/output-dev-skill-file of growthxai/output.

Open the folder on GitHubat commit ff9e1ab

Compare with similar skills

Output Dev Skill File next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Output Dev Skill File compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Output Dev Skill File this skillgrowthxai/output442—~2.1kAutomated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from growthxai/output

All 52 skills in this repo

  • LLM Output Schema Constraints

    growthxai/output

    Zod schema constraints that Anthropic rejects or silently ignores when sent as structured-output tool definitions via aiSdk.Output.object().

    442 GitHub stars~597 tokensUpdated yesterday
    Auto-check passed

  • Output Build Workflow

    growthxai/output

    Implement an Output SDK workflow from a plan document. An agent skill from growthxai/output.

    442 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Output Credentials Edit

    growthxai/output

    View, edit, and set encrypted credentials in an Output.ai project.

    442 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check: notes

  • Output Credentials Env Vars

    growthxai/output

    Wire encrypted credentials to environment variables using the credential: convention.

    442 GitHub stars~930 tokensUpdated yesterday
    Auto-check: notes

  • Output Credentials Init

    growthxai/output

    Initialize encrypted credentials for an Output.ai project. An agent skill from growthxai/output.

    442 GitHub stars~803 tokensUpdated yesterday
    Auto-check: notes

  • Output Debug Workflow

    growthxai/output

    Debug Output SDK workflow issues. An agent skill from growthxai/output.

    442 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Output Dev Skill File

What does Output Dev Skill File do?

Create .md skill files for Output framework's lazy-loaded instruction system. Output Dev Skill File is an agent skill from growthxai/output.md skill files for Output framework's lazy-loaded instruction system.

When should I use Output Dev Skill File?

Output Dev Skill File fits situations like: adding skills to prompts; configuring skill loading; debugging skill resolution.

How do I install Output Dev Skill File in Claude Code?

Run `npx skills add growthxai/output --skill output-dev-skill-file -a claude-code`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-dev-skill-file in growthxai/output) into .claude/skills/output-dev-skill-file in your project. Claude Code loads it when a task matches its description.

How do I install Output Dev Skill File in Codex?

Run `npx skills add growthxai/output --skill output-dev-skill-file -a codex`. Or copy the skill folder (coding_assistants/claude/plugins/outputai/skills/output-dev-skill-file in growthxai/output) into .agents/skills/output-dev-skill-file in your project. Codex loads it when a task matches its description.

Can I use Output Dev Skill File in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthxai/output --skill output-dev-skill-file -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/output-dev-skill-file, .gemini/skills/output-dev-skill-file, .github/skills/output-dev-skill-file and .opencode/skills/output-dev-skill-file in your project.

What does Output Dev Skill File need to run?

SKILL.md names no scripts, command-line tools or credentials: Output Dev Skill File is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit.

Does Output Dev Skill File access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Output Dev Skill File safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Output Dev Skill File use?

Output Dev Skill File is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Output Dev Skill File use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Output Dev Skill File?

Skills that share tags, products or a category with Output Dev Skill File: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Output Dev Skill File?

growthxai (a GitHub organization) maintains it in growthxai/output, which has 442 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 8, 2026.

Source: growthxai/output on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.