@riligar/agents-kit 1.8.0 → 1.9.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.agent/skills/riligar-business-startup-analyst/SKILL.md +2 -3
- package/.agent/skills/riligar-business-startup-financial/SKILL.md +2 -3
- package/.agent/skills/riligar-business-startup-market/SKILL.md +2 -3
- package/.agent/skills/riligar-design-system/SKILL.md +1 -1
- package/.agent/skills/riligar-dev-architecture/SKILL.md +1 -1
- package/.agent/skills/riligar-dev-auth-elysia/SKILL.md +1 -0
- package/.agent/skills/riligar-dev-auth-react/SKILL.md +1 -0
- package/.agent/skills/riligar-dev-autopilot/SKILL.md +2 -5
- package/.agent/skills/riligar-dev-backend/SKILL.md +3 -3
- package/.agent/skills/riligar-dev-clean-code/SKILL.md +2 -4
- package/.agent/skills/riligar-dev-code-review/SKILL.md +2 -2
- package/.agent/skills/riligar-dev-database/SKILL.md +2 -2
- package/.agent/skills/riligar-dev-frontend/SKILL.md +3 -3
- package/.agent/skills/riligar-dev-landing-page/SKILL.md +1 -1
- package/.agent/skills/riligar-dev-seo/SKILL.md +2 -2
- package/.agent/skills/riligar-dev-stripe/SKILL.md +152 -0
- package/.agent/skills/riligar-infrastructure/SKILL.md +1 -4
- package/.agent/skills/riligar-marketing-copy/SKILL.md +2 -2
- package/.agent/skills/riligar-marketing-email/SKILL.md +3 -2
- package/.agent/skills/riligar-marketing-seo/SKILL.md +2 -7
- package/.agent/skills/riligar-plan-writing/SKILL.md +1 -1
- package/.agent/skills/riligar-tech-stack/SKILL.md +1 -4
- package/.agent/skills/skill-creator/SKILL.md +37 -6
- package/package.json +1 -1
|
@@ -1,8 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-business-startup-analyst
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
|
|
3
|
+
type: business
|
|
4
|
+
description: Generate comprehensive investor-ready business case document with market, solution, financials, and strategy. Use when creating business cases for fundraising or strategic planning.
|
|
6
5
|
---
|
|
7
6
|
|
|
8
7
|
# Business Case Generator
|
|
@@ -1,8 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-business-startup-financial
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
|
|
3
|
+
type: business
|
|
4
|
+
description: Create detailed 3-5 year financial model with revenue, costs, cash flow, and scenarios. Use when building financial projections for startups or fundraising.
|
|
6
5
|
---
|
|
7
6
|
|
|
8
7
|
# Financial Projections
|
|
@@ -1,8 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-business-startup-market
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
|
|
3
|
+
type: business
|
|
4
|
+
description: Generate comprehensive market opportunity analysis with TAM/SAM/SOM calculations. Use when analyzing market size and opportunity for startups.
|
|
6
5
|
---
|
|
7
6
|
|
|
8
7
|
# Market Opportunity Analysis
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-design-system
|
|
3
|
+
type: design
|
|
3
4
|
description: Especialista no Sistema Visual da RiLiGar. Use para: (1) Criação de interfaces web e mobile (Light/Dark Mode), (2) Implementação de componentes UI (Mantine Only), (3) Garantir estética minimalista "Content-First", (4) Aplicar tokens de design via Mantine Theme.
|
|
4
|
-
license: Apache-2.0
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# RiLiGar Design System Expert
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-dev-architecture
|
|
3
|
+
type: development
|
|
3
4
|
description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
|
|
4
|
-
allowed-tools: Read, Glob, Grep
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Architecture Decision Framework
|
|
@@ -1,5 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-dev-auth-elysia
|
|
3
|
+
type: development
|
|
3
4
|
description: 'Comprehensive guide for integrating the Riligar Auth Elysia SDK into backend servers. Use when a user needs to: (1) Set up a backend auth plugin, (2) Configure Elysia with Riligar Secret Key, (3) Protect API routes or groups, (4) Access authenticated user data in handlers, (5) Perform manual JWT verification.'
|
|
4
5
|
---
|
|
5
6
|
|
|
@@ -1,5 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-dev-auth-react
|
|
3
|
+
type: development
|
|
3
4
|
description: 'Comprehensive guide for integrating the Riligar Auth React SDK into web applications. Use when a user needs to: (1) Set up authentication from scratch, (2) Configure AuthProvider, (3) Implement route protection, (4) Use auth hooks or pre-built UI components, (5) Handle login/signup/profile/magic links in React.'
|
|
4
5
|
---
|
|
5
6
|
|
|
@@ -1,10 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-dev-autopilot
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
metadata:
|
|
6
|
-
author: riligar
|
|
7
|
-
version: '1.0'
|
|
3
|
+
type: development
|
|
4
|
+
description: Automação do ciclo de vida de desenvolvimento. Validação com Bun, Auto-correção, Commit Semântico e Deploy. Use para garantir código funcional e entregue em produção.
|
|
8
5
|
---
|
|
9
6
|
|
|
10
7
|
# RiLiGar Dev-Autopilot Expert
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: riligar-dev-
|
|
3
|
-
|
|
4
|
-
|
|
2
|
+
name: riligar-dev-backend
|
|
3
|
+
type: development
|
|
4
|
+
description: API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination. Use when designing APIs or backend services.
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# API Patterns
|
|
@@ -1,9 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-dev-clean-code
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
version: 2.1
|
|
6
|
-
priority: CRITICAL
|
|
3
|
+
type: development
|
|
4
|
+
description: Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments. CRITICAL skill that defines RiLiGar coding standards. Use when writing or reviewing any code.
|
|
7
5
|
---
|
|
8
6
|
|
|
9
7
|
# Clean Code - Pragmatic AI Coding Standards (RiLiGar)
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-dev-code-review
|
|
3
|
-
|
|
4
|
-
|
|
3
|
+
type: development
|
|
4
|
+
description: Code review guidelines covering code quality, security, and best practices. Use when reviewing code or creating review checklists.
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Code Review Checklist
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-dev-database
|
|
3
|
-
|
|
4
|
-
|
|
3
|
+
type: development
|
|
4
|
+
description: Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases. Use when designing schemas or optimizing database performance.
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Database Design
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: riligar-dev-
|
|
3
|
-
|
|
4
|
-
|
|
2
|
+
name: riligar-dev-frontend
|
|
3
|
+
type: development
|
|
4
|
+
description: Modern React patterns and principles. Hooks, composition, performance, and JavaScript best practices. Use when building React components, managing state, or implementing UI patterns.
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# React Patterns
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-dev-landing-page
|
|
3
|
+
type: development
|
|
3
4
|
description: Specialist in High-Conversion Landing Pages using RiLiGar Design System. Use for: (1) Creating marketing/sales pages, (2) Structuring conversion flows (AIDA/PAS), (3) Implementing high-trust components (Hero, Social Proof, Pricing), (4) Writing persuasive copy.
|
|
4
|
-
license: Apache-2.0
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# RiLiGar Landing Page Architect
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-dev-seo
|
|
3
|
-
|
|
4
|
-
|
|
3
|
+
type: development
|
|
4
|
+
description: Implementação de infraestrutura de SEO técnico seguindo a stack RiLiGar (React, Vite, Bun, Elysia). Use para configurar sitemaps, robots.txt, meta tags, OpenGraph, dados estruturados (JSON-LD) e URLs canônicas.
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# SEO Técnico (RiLiGar Tech Stack)
|
|
@@ -0,0 +1,152 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: riligar-dev-stripe
|
|
3
|
+
type: development
|
|
4
|
+
description: Stripe payment integration patterns. Use when implementing payments, subscriptions, webhooks, checkout flows, or billing in Elysia/Bun applications.
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Stripe Integration Patterns
|
|
8
|
+
|
|
9
|
+
> Patterns for integrating Stripe payments in RiLiGar applications.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Mandatory Guidelines
|
|
14
|
+
|
|
15
|
+
> [!IMPORTANT]
|
|
16
|
+
> All work in this skill MUST adhere to:
|
|
17
|
+
>
|
|
18
|
+
> - @[.agent/skills/riligar-dev-backend] (API Standards)
|
|
19
|
+
> - @[.agent/skills/riligar-dev-clean-code] (Clean Code Standards)
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## 1. Core Concepts
|
|
24
|
+
|
|
25
|
+
| Concept | Description |
|
|
26
|
+
| --- | --- |
|
|
27
|
+
| **Customer** | User identity in Stripe |
|
|
28
|
+
| **Product** | What you're selling |
|
|
29
|
+
| **Price** | How much and billing cycle |
|
|
30
|
+
| **Subscription** | Recurring payment |
|
|
31
|
+
| **PaymentIntent** | One-time payment |
|
|
32
|
+
| **Webhook** | Event notifications |
|
|
33
|
+
|
|
34
|
+
---
|
|
35
|
+
|
|
36
|
+
## 2. Environment Setup
|
|
37
|
+
|
|
38
|
+
```bash
|
|
39
|
+
# .env
|
|
40
|
+
STRIPE_SECRET_KEY=sk_live_...
|
|
41
|
+
STRIPE_WEBHOOK_SECRET=whsec_...
|
|
42
|
+
STRIPE_PUBLISHABLE_KEY=pk_live_...
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
> [!IMPORTANT]
|
|
46
|
+
> Never expose `STRIPE_SECRET_KEY` in frontend code.
|
|
47
|
+
|
|
48
|
+
---
|
|
49
|
+
|
|
50
|
+
## 3. Server-Side Patterns (Elysia)
|
|
51
|
+
|
|
52
|
+
### Initialize Stripe
|
|
53
|
+
|
|
54
|
+
```javascript
|
|
55
|
+
import Stripe from 'stripe'
|
|
56
|
+
|
|
57
|
+
const stripe = new Stripe(process.env.STRIPE_SECRET_KEY)
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
### Create Checkout Session
|
|
61
|
+
|
|
62
|
+
```javascript
|
|
63
|
+
const session = await stripe.checkout.sessions.create({
|
|
64
|
+
mode: 'subscription',
|
|
65
|
+
customer_email: user.email,
|
|
66
|
+
line_items: [{ price: priceId, quantity: 1 }],
|
|
67
|
+
success_url: `${baseUrl}/success?session_id={CHECKOUT_SESSION_ID}`,
|
|
68
|
+
cancel_url: `${baseUrl}/cancel`,
|
|
69
|
+
})
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
### Webhook Handler
|
|
73
|
+
|
|
74
|
+
```javascript
|
|
75
|
+
app.post('/webhook/stripe', async ({ request, set }) => {
|
|
76
|
+
const sig = request.headers.get('stripe-signature')
|
|
77
|
+
const body = await request.text()
|
|
78
|
+
|
|
79
|
+
const event = stripe.webhooks.constructEvent(
|
|
80
|
+
body,
|
|
81
|
+
sig,
|
|
82
|
+
process.env.STRIPE_WEBHOOK_SECRET
|
|
83
|
+
)
|
|
84
|
+
|
|
85
|
+
switch (event.type) {
|
|
86
|
+
case 'checkout.session.completed':
|
|
87
|
+
await handleCheckoutComplete(event.data.object)
|
|
88
|
+
break
|
|
89
|
+
case 'customer.subscription.updated':
|
|
90
|
+
await handleSubscriptionUpdate(event.data.object)
|
|
91
|
+
break
|
|
92
|
+
case 'customer.subscription.deleted':
|
|
93
|
+
await handleSubscriptionCancel(event.data.object)
|
|
94
|
+
break
|
|
95
|
+
}
|
|
96
|
+
|
|
97
|
+
return { received: true }
|
|
98
|
+
})
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
---
|
|
102
|
+
|
|
103
|
+
## 4. Essential Webhooks
|
|
104
|
+
|
|
105
|
+
| Event | When to Handle |
|
|
106
|
+
| --- | --- |
|
|
107
|
+
| `checkout.session.completed` | Provision access after payment |
|
|
108
|
+
| `customer.subscription.updated` | Plan changes, renewals |
|
|
109
|
+
| `customer.subscription.deleted` | Cancellation |
|
|
110
|
+
| `invoice.payment_failed` | Payment issues |
|
|
111
|
+
| `invoice.paid` | Successful recurring payment |
|
|
112
|
+
|
|
113
|
+
---
|
|
114
|
+
|
|
115
|
+
## 5. Customer Portal
|
|
116
|
+
|
|
117
|
+
```javascript
|
|
118
|
+
const portalSession = await stripe.billingPortal.sessions.create({
|
|
119
|
+
customer: customerId,
|
|
120
|
+
return_url: `${baseUrl}/account`,
|
|
121
|
+
})
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
---
|
|
125
|
+
|
|
126
|
+
## 6. Security Checklist
|
|
127
|
+
|
|
128
|
+
- [ ] Verify webhook signatures
|
|
129
|
+
- [ ] Use idempotency keys for retries
|
|
130
|
+
- [ ] Store customer ID in database
|
|
131
|
+
- [ ] Handle edge cases (expired cards, disputes)
|
|
132
|
+
- [ ] Test with Stripe CLI locally
|
|
133
|
+
|
|
134
|
+
---
|
|
135
|
+
|
|
136
|
+
## 7. Testing
|
|
137
|
+
|
|
138
|
+
```bash
|
|
139
|
+
# Install Stripe CLI
|
|
140
|
+
brew install stripe/stripe-cli/stripe
|
|
141
|
+
|
|
142
|
+
# Forward webhooks to local server
|
|
143
|
+
stripe listen --forward-to localhost:3000/webhook/stripe
|
|
144
|
+
```
|
|
145
|
+
|
|
146
|
+
---
|
|
147
|
+
|
|
148
|
+
## Related Skills
|
|
149
|
+
|
|
150
|
+
- @[.agent/skills/riligar-dev-backend]
|
|
151
|
+
- @[.agent/skills/riligar-dev-auth-elysia]
|
|
152
|
+
- @[.agent/skills/riligar-tech-stack]
|
|
@@ -1,10 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-infrastructure
|
|
3
|
+
type: infrastructure
|
|
3
4
|
description: Especialista em Infraestrutura da RiLiGar. Use para configurar deployments no Fly.io, DNS e proxying no Cloudflare, e garantir padrões de infraestrutura e deployment.
|
|
4
|
-
license: Apache-2.0
|
|
5
|
-
metadata:
|
|
6
|
-
author: riligar
|
|
7
|
-
version: '1.0'
|
|
8
5
|
---
|
|
9
6
|
|
|
10
7
|
# RiLiGar Infrastructure Expert
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-marketing-copy
|
|
3
|
-
|
|
4
|
-
|
|
3
|
+
type: marketing
|
|
4
|
+
description: Generate compelling marketing copy using the Elevated Direct Response framework. Use when creating landing pages, headlines, email campaigns, ad copy, CTAs, value propositions, or any persuasive marketing content.
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Elevated Direct Response Copywriter
|
|
@@ -1,6 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: email
|
|
3
|
-
|
|
2
|
+
name: riligar-marketing-email
|
|
3
|
+
type: marketing
|
|
4
|
+
description: Email sequence design and optimization. Use when creating drip campaigns, automated flows, nurture sequences, onboarding emails, welcome sequences, re-engagement emails, or lifecycle email programs.
|
|
4
5
|
---
|
|
5
6
|
|
|
6
7
|
# Email Sequence Design
|
|
@@ -1,12 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-marketing-seo
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
at scale using templates and structured data. Use when the user mentions
|
|
6
|
-
programmatic SEO, pages at scale, template pages, directory pages, location pages,
|
|
7
|
-
comparison pages, integration pages, or keyword-pattern page generation.
|
|
8
|
-
This skill focuses on feasibility, strategy, and page system design—not execution
|
|
9
|
-
unless explicitly requested.
|
|
3
|
+
type: marketing
|
|
4
|
+
description: Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale. Use when working with programmatic SEO, template pages, directory pages, location pages, or keyword-pattern page generation.
|
|
10
5
|
---
|
|
11
6
|
|
|
12
7
|
---
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-plan-writing
|
|
3
|
+
type: development
|
|
3
4
|
description: Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
|
|
4
|
-
allowed-tools: Read, Glob, Grep
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Plan Writing
|
|
@@ -1,10 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: riligar-tech-stack
|
|
3
|
+
type: development
|
|
3
4
|
description: Especialista na Tech Stack da RiLiGar. Use para criar projetos React/Vite, componentes com Mantine, APIs Bun/Elysia, e garantir padrões de código e estrutura de projetos.
|
|
4
|
-
license: Apache-2.0
|
|
5
|
-
metadata:
|
|
6
|
-
author: riligar
|
|
7
|
-
version: '1.0'
|
|
8
5
|
---
|
|
9
6
|
|
|
10
7
|
# RiLiGar Tech Stack Expert
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: skill-creator
|
|
3
|
-
|
|
4
|
-
|
|
3
|
+
type: meta
|
|
4
|
+
description: Guide for creating effective skills. Use when creating a new skill or updating an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
# Skill Creator
|
|
@@ -53,6 +53,7 @@ skill-name/
|
|
|
53
53
|
├── SKILL.md (required)
|
|
54
54
|
│ ├── YAML frontmatter metadata (required)
|
|
55
55
|
│ │ ├── name: (required)
|
|
56
|
+
│ │ ├── type: (required)
|
|
56
57
|
│ │ └── description: (required)
|
|
57
58
|
│ └── Markdown instructions (required)
|
|
58
59
|
└── Bundled Resources (optional)
|
|
@@ -61,11 +62,30 @@ skill-name/
|
|
|
61
62
|
└── assets/ - Files used in output (templates, icons, fonts, etc.)
|
|
62
63
|
```
|
|
63
64
|
|
|
65
|
+
### Skill Types (Taxonomy)
|
|
66
|
+
|
|
67
|
+
Every skill must have a `type` field that categorizes it. This enables organization, filtering, and discovery.
|
|
68
|
+
|
|
69
|
+
| Type | Description | Naming Pattern |
|
|
70
|
+
| --- | --- | --- |
|
|
71
|
+
| `development` | Software development skills (frontend, backend, database, architecture, auth, testing) | `riligar-dev-*` |
|
|
72
|
+
| `design` | UI/UX and visual design skills | `riligar-design-*` |
|
|
73
|
+
| `marketing` | Copywriting, email, SEO, and content marketing | `riligar-marketing-*` |
|
|
74
|
+
| `business` | Business analysis, financial modeling, market research | `riligar-business-*` |
|
|
75
|
+
| `infrastructure` | Deployment, DNS, hosting, DevOps | `riligar-infrastructure` |
|
|
76
|
+
| `meta` | Skills about skills (this skill) | `skill-creator` |
|
|
77
|
+
|
|
78
|
+
**Naming Convention:**
|
|
79
|
+
|
|
80
|
+
- Directory name MUST match the `name` field in frontmatter
|
|
81
|
+
- Use pattern: `riligar-{type}-{specific-name}`
|
|
82
|
+
- Examples: `riligar-dev-frontend`, `riligar-marketing-copy`, `riligar-business-startup-analyst`
|
|
83
|
+
|
|
64
84
|
#### SKILL.md (required)
|
|
65
85
|
|
|
66
86
|
Every SKILL.md consists of:
|
|
67
87
|
|
|
68
|
-
- **Frontmatter** (YAML): Contains `name` and `description` fields. These are the only fields that Claude reads to determine when the skill gets used, thus it is very important to be clear and comprehensive in describing what the skill is, and when it should be used.
|
|
88
|
+
- **Frontmatter** (YAML): Contains `name`, `type`, and `description` fields. These are the only fields that Claude reads to determine when the skill gets used, thus it is very important to be clear and comprehensive in describing what the skill is, and when it should be used.
|
|
69
89
|
- **Body** (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers (if at all).
|
|
70
90
|
|
|
71
91
|
#### Bundled Resources (optional)
|
|
@@ -303,15 +323,26 @@ Any example files and directories not needed for the skill should be deleted. Th
|
|
|
303
323
|
|
|
304
324
|
##### Frontmatter
|
|
305
325
|
|
|
306
|
-
Write the YAML frontmatter with `name` and `description`:
|
|
326
|
+
Write the YAML frontmatter with `name`, `type`, and `description`:
|
|
307
327
|
|
|
308
|
-
- `name`: The skill name
|
|
328
|
+
- `name`: The skill name (must match directory name)
|
|
329
|
+
- `type`: The skill category (see Skill Types taxonomy above)
|
|
309
330
|
- `description`: This is the primary triggering mechanism for your skill, and helps Claude understand when to use the skill.
|
|
310
331
|
- Include both what the Skill does and specific triggers/contexts for when to use it.
|
|
311
332
|
- Include all "when to use" information here - Not in the body. The body is only loaded after triggering, so "When to Use This Skill" sections in the body are not helpful to Claude.
|
|
312
333
|
- Example description for a `docx` skill: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. Use when Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
|
|
313
334
|
|
|
314
|
-
|
|
335
|
+
**Example frontmatter:**
|
|
336
|
+
|
|
337
|
+
```yaml
|
|
338
|
+
---
|
|
339
|
+
name: riligar-dev-example
|
|
340
|
+
type: development
|
|
341
|
+
description: Brief description of what the skill does. Use when [specific triggers].
|
|
342
|
+
---
|
|
343
|
+
```
|
|
344
|
+
|
|
345
|
+
Do not include any other fields in YAML frontmatter (no `allowed-tools`, `license`, `metadata`, `version`, etc.).
|
|
315
346
|
|
|
316
347
|
##### Body
|
|
317
348
|
|