Back to marketplace

Write A Skill

Create new agent skills with proper structure, progressive disclosure, and bundled resources.

Development / Engineeringdevelopmentengineering
by AgentVoltv1.0.0Published 1y ago1 install
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Create a new Claude skill for managing our internal project workflows”
Beforegeneric AI agent
Creating a custom Claude skill for your project workflows is a good idea for automating repetitive tasks. You'd want to think about what specific workflow you're trying to handle—are you looking to automate task creation, status updates, team communication? You'd need to define the input format (what information the skill needs), the logic (how Claude should process that information), and the output (what the skill should produce).

You might also consider how the skill integrates with your existing tools—Jira, Asana, Slack, whatever you're using. The key is to make it reusable so you can apply it across multiple projects. Do you have existing documentation or examples of the workflow you want to automate? That would help me understand the scope better.
Afterwith Write A Skill
SKILL CREATION TEMPLATE: Project Workflow Automation

SKILL METADATA:
   Name: Project Workflow Orchestrator
   Slug: project-workflow-orchestrator
   Trigger: "Set up a workflow for task X" or "Automate our project intake"
   Category: ops / project-management
   Description: Converts project descriptions into structured task lists, assigns to team, syncs to Jira/Asana

STRUCTURED SKILL.MD COMPONENTS:

## What You Get
   • Workflow template (inputs, outputs, decision tree)
   • Integration patterns (Jira API, Slack notifications, Google Sheets logs)
   • Progressive disclosure (basic workflow, then advanced customization)

## Progressive Disclosure (User ramps up gradually)
   LEVEL 1: Out-of-box workflow
   → User pastes project description, skill outputs Jira issue + task list + Slack thread
   
   LEVEL 2: Customization
   → User can modify: due date rules, team assignments, priority logic
   
   LEVEL 3: Advanced
   → User creates custom decision tree ("If feature request, then QA, then legal review")

## Input Contract
   Input: Project description (free text, 100-500 words)
   Required fields:
      • Project name
      • Deadline (date)
      • Team (list of names)
      • Success criteria (bulleted)
   Optional fields:
      • Budget
      • Risk flags
      • Dependencies (other projects)

## Processing Logic
   1. Parse project description → Extract scope, timeline, risks
   2. Generate task breakdown → 8-12 tasks, sequenced with dependencies
   3. Assign to team → Match skills (engineer, designer, PM) to task types
   4. Create Jira issues → One issue per task, add acceptance criteria
   5. Notify team → Slack message in #projects with thread link
   6. Log to spreadsheet → Audit trail: who, what, when

## Output Contract
   Deliverables:
      • Structured task list (TSV export)
      • Jira epic + issues (linked)
      • Slack thread (team notification + links)
      • Workflow diagram (as text, ASCII swimlanes)
   
   Example output for "Build new checkout flow":
   
   TASK BREAKDOWN:
      1. Design system audit [Designer, 2d] → Prerequisite for task #3
      2. Wireframe flows [PM, 1d] → Depends on #1
      3. Front-end implementation [Engineer, 4d] → Depends on #2
      4. Payment provider integration [Engineer, 3d] → Parallel to #3
      5. QA & testing [QA, 2d] → Depends on #3, #4
      6. Monitoring setup [DevOps, 1d] → Depends on deployment
      7. Launch & comms [PM, 1d] → Last step
   
   Swimlane diagram:
      Design   |---[Audit]--|
      PM       |----[Wireframe]----|
      Engineer |--[Impl]--|--[Integrate]--|
      QA       |--[Test]--|
      DevOps   |--[Monitor]--|
   
   JIRA Config:
      Epic: "Build Checkout Flow"
      Issues created: 7
      Team assignments: Designer (Sarah), PM (James), Engineers (Raj, Lei)
      Sprint: Sprint 34 (8 days)
   
   Slack notification:
      "Checkout flow project initialized. 7 tasks across 5 people."
      Links: Jira epic | Swimlane diagram | Task spreadsheet

## Customization Examples (Bundled in skill resources)
   • Legal review gate: If project touches payments → trigger legal review before launch
   • Multi-region deployment: If global launch → add locale testing task per region
   • Customer communication: If customer-facing → add comms/blog task before launch

## Integration Points (Resources bundled)
   Jira API: Issue creation template, epic linking, workflow transition rules
   Slack: Message formatting, thread replies, notification channel mapping
   Google Sheets: Append-only audit log schema
   Markdown: Swimlane ASCII rendering

## Error Handling
   • Missing deadline → Skill asks: "When should this ship?"
   • Unrecognized team member → Skill suggests: "Did you mean Sarah or Sam?"
   • Over-scoped project (>20 tasks) → Skill warns: "This looks like 2 projects. Split it?"

## Testing Checklist (Bundled)
   ✓ Task count reasonable (8-15)
   ✓ Dependencies sensible (no circular loops)
   ✓ Team coverage complete (no orphaned tasks)
   ✓ Timeline realistic (no 3-person task day 1 + day 2)
   ✓ Jira issues created and linked
   ✓ Slack message posted in correct channel
   ✓ Audit log entry written

## Best For
   Product teams running 3+ concurrent projects, PM-led organizations, teams needing audit trails

RESOURCES BUNDLED (Included with skill):
   • reference-workflow-templates.md (8 common project archetypes)
   • jira-api-keys.md (setup instructions, not keys themselves)
   • slack-channel-mapping.json (which channels get which notifications)
   • swimlane-template.txt (ASCII diagram format)
   • audit-log-schema.sql (Google Sheets append format)

VERSION TRACKING:
   Version: 1.0
   Last updated: 2024-11-15
   Maintainer: Internal ops team
   Changelog: (Log customizations & improvements here)

About this skill

name: write-a-skill description: Use when Create new agent skills with proper structure, progressive disclosure, and bundled resources.

Write A Skill

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.

What you get

  • Public GitHub repo (alirezarezvani/claude-skills)
  • the write-a-skill skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.

Customize your output

  • Fork the repo and adapt the skill's instructions and references to your workflow.

Example output

Activates automatically when your request matches Write A Skill; chains with the other skills, agents, and commands in the collection.

Best for

Creators, builders, and teams using Claude Code.

SKILL.md preview

SKILL.md
---
name: write-a-skill
description: Use this skill when the user wants to create, write, build, or author a new agent skill with proper structure, progressive disclosure, and bundled resources.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
  - development
  - engineering
---

# Write A Skill

Authors new agent skills that follow proper structure — clear triggering description, progressive disclosure of detail, and correctly bundled supporting resources.

## When to use

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More development skills

View all Development skills →

Generate

Scaffold code, tests, and boilerplate from a short spec.

Development

Performance Profiler

Systematic performance profiling for Node.js, Python, and Go applications.

Development

Threat Detection

Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.

Development

Agent Harness

Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.

Development