skill-builder

Design new skills or agents with canonical workflows and governance rules.

55|8|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/j1ngg/tech-marketing-framework --skill skill-builder-j1ngg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-builder
Source: https://github.com/j1ngg/tech-marketing-framework/tree/main/.agents/skills/skill-builder
Command: npx skills add https://github.com/j1ngg/tech-marketing-framework --skill skill-builder-j1ngg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps teams design a new skill or agent and select the appropriate pattern, structure, and governance rules.

Core Features & Use Cases

  • Guidance on selecting patterns and templates for new skills or agents across repository types.
  • Reference implementations and canonical workflow to align with existing guidelines.
  • Real-world usage: when starting a new skill, you can rely on the tool to map requirements to the right structure and checks.

Quick Start

Follow the canonical workflow to design your next skill or agent.

Frequently Asked Questions about skill-builder

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

FAQPage Schema
How do I plan and structure a new agent or skill design?

To plan and structure a new agent or skill design, identify the appropriate pattern, structure, and governing rules by applying a canonical workflow during the design phase to ensure alignment with existing repository guidelines and templates.

What is the canonical workflow for designing an agent?

The canonical workflow for designing an agent maps your requirements to the right structure and checks, ensuring consistency with shared documentation rules and satisfying frontmatter requirements for name and description.

How do I select the right pattern and templates for a new skill across different repositories?

Select the right pattern and templates for a new skill by referencing canonical implementations during the design phase to map requirements across repository contexts and align with existing guidelines.

Do I need frontmatter requirements to structure an agent design?

Yes, structuring an agent design requires frontmatter with name and description to satisfy consistency with shared documentation rules and align with existing workflow guidelines.

What's the best way to ensure a new skill aligns with existing documentation rules?

The best way to ensure a new skill aligns with existing documentation rules is to apply the canonical workflow during the design phase to check consistency with shared templates and governing guidelines across repository contexts.