skill-authoring

Create reusable skill files with SKILL.md frontmatter and usage instructions.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/4tie/fortiesr --skill skill-authoring-4tie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-authoring
Source: https://github.com/4tie/fortiesr/tree/main/.local/skills/skill-authoring
Command: npx skills add https://github.com/4tie/fortiesr --skill skill-authoring-4tie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you capture a repeatable workflow once so you can reuse it across future sessions instead of rewriting instructions each time.

Core Features & Use Cases

  • Reusable instructions: Save a concise operating playbook for tasks you expect to repeat.
  • Skill design guidance: Define when to use the skill, what to include, and how to keep it maintainable.
  • Use case: Turn a one-off process like report drafting, code review, or document parsing into a durable agent capability.

Quick Start

Ask the assistant to turn a recurring workflow into a new skill with a clear name, a short description, and step-by-step instructions.

Frequently Asked Questions about skill-authoring

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

FAQPage Schema
How do I turn repeatable workflows into reusable instructions for future sessions?▼

You can turn repeatable workflows into reusable instructions by creating a skill file with a named trigger, concise operating guidance, and a root SKILL.md containing valid markdown frontmatter. This packages your recurring tasks into portable agent instructions.

What is a reusable skill file and when do I need to create one?▼

A reusable skill file is a portable set of agent instructions that packages a recurring workflow. You need to create one when you expect to repeat a task, such as report drafting or code review, and want to avoid rewriting instructions each time.

How do I structure a SKILL.md file with frontmatter for agent instructions?▼

To structure a SKILL.md file, include valid markdown frontmatter at the root, clear usage instructions defining when to use the skill, and supporting components like scripts or references only when the workflow needs additional assets.

Do I need to include scripts and reference components in every skill file?▼

No, you do not need to include scripts and reference components in every skill file. Supporting components are only required when the specific workflow needs scripts, references, or assets beyond the concise operating playbook in the SKILL.md.

What is the best way to design a maintainable skill for a recurring task?▼

The best way to design a maintainable skill is to define a clear name, a short description, and concise step-by-step instructions. Keep it maintainable by defining exactly when to use the skill and what to include.

Can I use markdown frontmatter to define named triggers for prompt engineering workflows?▼

Yes, you can use markdown frontmatter to define named triggers for prompt engineering workflows. The root SKILL.md requires valid frontmatter to establish the named trigger and concise operating guidance for the agent.