claude-skills-cli 0.0.4 → 0.0.5

package/{skills → dist/skills}/skill-creator/references/skill-examples.md

@@ -6,7 +6,8 @@ Real examples showing effective skill patterns using TypeScript/Node.
 
 ### Use Case
 
-Repeatedly making authenticated API requests with TypeScript types and error handling.
+Repeatedly making authenticated API requests with TypeScript types and
+error handling.
 
 ### Structure
 
@@ -27,7 +28,10 @@ api-client/
 ````markdown
 ---
 name: api-client
-description: REST API client with TypeScript types for user and data endpoints. Use when making HTTP requests, handling authentication, managing API errors, or working with async operations.
+description:
+  REST API client with TypeScript types for user and data endpoints.
+  Use when making HTTP requests, handling authentication, managing API
+  errors, or working with async operations.
 ---
 
 # API Client
@@ -42,7 +46,8 @@ const user = await apiClient.get<User>(`/users/${id}`);
 ```
 ````
 
-For complete endpoint docs: [references/endpoints.md](references/endpoints.md)
+For complete endpoint docs:
+[references/endpoints.md](references/endpoints.md)
 
 ```
 
@@ -63,16 +68,11 @@ Creating type-safe React components with hooks and TypeScript interfaces.
 ### Structure
 ```
 
-react-patterns/
-├── SKILL.md # Core patterns and conventions
-├── references/
-│ ├── component-library.md # Catalog of existing components
-│ ├── hooks-patterns.md # Custom hooks and state management
-│ └── routing-patterns.md # React Router conventions
-└── assets/
-└── component-templates/
-├── basic-component.tsx
-├── form-component.tsx
+react-patterns/ ├── SKILL.md # Core patterns and conventions ├──
+references/ │ ├── component-library.md # Catalog of existing
+components │ ├── hooks-patterns.md # Custom hooks and state management
+│ └── routing-patterns.md # React Router conventions └── assets/ └──
+component-templates/ ├── basic-component.tsx ├── form-component.tsx
 └── list-component.tsx
 
 ````
@@ -108,7 +108,8 @@ export function Card({ title, items }: CardProps) {
 }
 ````
 
-For complete component library: [references/component-library.md](references/component-library.md)
+For complete component library:
+[references/component-library.md](references/component-library.md)
 
 ```
 
@@ -129,14 +130,11 @@ Implementing GitHub OAuth, fetching profiles, managing connections.
 ### Structure
 ```
 
-github-integration/
-├── SKILL.md # Auth patterns, common operations
-├── references/
-│ ├── api-endpoints.md # GitHub API reference
-│ └── oauth-flow.md # Complete OAuth implementation
-└── scripts/
-├── test_connection.js # Validate GitHub credentials
-└── check_rate_limit.js # Monitor API usage
+github-integration/ ├── SKILL.md # Auth patterns, common operations
+├── references/ │ ├── api-endpoints.md # GitHub API reference │ └──
+oauth-flow.md # Complete OAuth implementation └── scripts/ ├──
+test_connection.js # Validate GitHub credentials └──
+check_rate_limit.js # Monitor API usage
 
 ````
 
@@ -183,13 +181,10 @@ Consistent component styling, theme usage, form patterns.
 ### Structure
 ```
 
-daisyui-conventions/
-├── SKILL.md # Core components and patterns
-├── references/
-│ ├── component-reference.md # All DaisyUI components
-│ └── theme-tokens.md # Color system and usage
-└── assets/
-└── theme-preview.html # Visual reference
+daisyui-conventions/ ├── SKILL.md # Core components and patterns ├──
+references/ │ ├── component-reference.md # All DaisyUI components │
+└── theme-tokens.md # Color system and usage └── assets/ └──
+theme-preview.html # Visual reference
 
 ````
 
@@ -213,7 +208,8 @@ description: DaisyUI v5 component styling for cards, forms, buttons, and layouts
 </div>
 ````
 
-For all components: [references/component-reference.md](references/component-reference.md)
+For all components:
+[references/component-reference.md](references/component-reference.md)
 
 ````
 
@@ -242,7 +238,10 @@ description: Helps with API stuff
 ### After (Specific)
 
 ```yaml
-description: REST API client with TypeScript types for user and data endpoints. Use when making HTTP requests, handling authentication, managing API errors, or working with async operations.
+description:
+  REST API client with TypeScript types for user and data endpoints.
+  Use when making HTTP requests, handling authentication, managing API
+  errors, or working with async operations.
 ```
 
 ---
@@ -282,9 +281,8 @@ description: [50-100 words with keywords]
 ### Without Script
 
 ```markdown
-Claude generates validation code every time:
-"Check that all timestamps are valid..."
-[Claude writes 50 lines of JavaScript]
+Claude generates validation code every time: "Check that all
+timestamps are valid..." [Claude writes 50 lines of JavaScript]
 ```
 
 **Cost**: ~500 tokens each time
@@ -311,8 +309,8 @@ node scripts/validate_timestamps.js
 ### Without Assets
 
 ```markdown
-"Create a basic Svelte component..."
-[Claude writes boilerplate each time]
+"Create a basic Svelte component..." [Claude writes boilerplate each
+time]
 ```
 
 ### With Assets
@@ -374,7 +372,8 @@ description: Helps with frontend stuff
 
 ## Skill Composition Example
 
-**User Request**: "Create a user profile card with API data and styling"
+**User Request**: "Create a user profile card with API data and
+styling"
 
 **Skills Activated**:
 
@@ -406,6 +405,9 @@ Before considering a skill "done":
 
 ## Resources
 
-- See main [SKILLS-ARCHITECTURE.md](../../../docs/SKILLS-ARCHITECTURE.md) for system design
-- See [SKILL-EXAMPLES.md](../../../docs/SKILL-EXAMPLES.md) for Anthropic examples
+- See main
+  [SKILLS-ARCHITECTURE.md](../../../docs/SKILLS-ARCHITECTURE.md) for
+  system design
+- See [SKILL-EXAMPLES.md](../../../docs/SKILL-EXAMPLES.md) for
+  Anthropic examples
 - See skill-creator SKILL.md for 6-step process

package/{skills → dist/skills}/skill-creator/references/writing-guide.md

@@ -11,19 +11,17 @@ Claude responds best to direct instructions.
 #### ✅ Good Examples
 
 ```markdown
-Use prepared statements for all database queries.
-Generate IDs with nanoid() before inserting records.
-Store timestamps as Unix epoch milliseconds.
-Validate input before saving to database.
+Use prepared statements for all database queries. Generate IDs with
+nanoid() before inserting records. Store timestamps as Unix epoch
+milliseconds. Validate input before saving to database.
 ```
 
 #### ❌ Bad Examples
 
 ```markdown
-You should use prepared statements for database queries.
-You'll want to generate IDs with nanoid().
-It's best if you store timestamps as Unix epoch.
-Try to validate input before saving.
+You should use prepared statements for database queries. You'll want
+to generate IDs with nanoid(). It's best if you store timestamps as
+Unix epoch. Try to validate input before saving.
 ```
 
 ### Be Specific, Not Vague
@@ -42,9 +40,9 @@ const timestamp = new Date().toISOString();
 
 // Use type-safe interfaces
 interface User {
-  id: string;
-  name: string;
-  email: string;
+	id: string;
+	name: string;
+	email: string;
 }
 ```
 
@@ -79,15 +77,16 @@ To fetch user data:
 #### ❌ Bad (Conceptual)
 
 ```markdown
-When thinking about API design, consider REST principles
-and how architectural patterns affect your implementation...
+When thinking about API design, consider REST principles and how
+architectural patterns affect your implementation...
 ```
 
 ---
 
 ## Description Writing
 
-The description determines when Claude triggers your skill. Make it count.
+The description determines when Claude triggers your skill. Make it
+count.
 
 ### Description Formula
 
@@ -100,7 +99,10 @@ The description determines when Claude triggers your skill. Make it count.
 #### API Client Skill
 
 ```yaml
-description: REST API client for user data endpoints with TypeScript types. Use when making HTTP requests, handling authentication, or working with API responses and error handling.
+description:
+  REST API client for user data endpoints with TypeScript types. Use
+  when making HTTP requests, handling authentication, or working with
+  API responses and error handling.
 ```
 
 **Breakdown**:
@@ -113,7 +115,10 @@ description: REST API client for user data endpoints with TypeScript types. Use
 #### Component Skill
 
 ```yaml
-description: Create type-safe React components with hooks and TypeScript interfaces. Use when building UI components, implementing forms, or managing component state and props.
+description:
+  Create type-safe React components with hooks and TypeScript
+  interfaces. Use when building UI components, implementing forms, or
+  managing component state and props.
 ```
 
 **Breakdown**:
@@ -182,10 +187,10 @@ const users = await apiClient.get<User[]>('/users');
 
 ```typescript
 const newUser = await apiClient.post<User>('/users', {
-  id: nanoid(),
-  name: 'John Doe',
-  email: 'john@example.com',
-  createdAt: new Date().toISOString(),
+	id: nanoid(),
+	name: 'John Doe',
+	email: 'john@example.com',
+	createdAt: new Date().toISOString(),
 });
 ```
 
@@ -231,10 +236,10 @@ Pull examples from actual codebase, not invented scenarios.
 ```typescript
 // From src/lib/api/users.ts
 const response = await fetch(`${API_BASE}/users/${userId}/stats`, {
-  headers: {
-    Authorization: `Bearer ${token}`,
-    'Content-Type': 'application/json',
-  },
+	headers: {
+		Authorization: `Bearer ${token}`,
+		'Content-Type': 'application/json',
+	},
 });
 const stats = (await response.json()) as UserStats;
 ```
@@ -256,15 +261,17 @@ import { nanoid } from 'nanoid';
 import type { User, CreateUserRequest } from './types';
 import { apiClient } from './client';
 
-const createUser = async (request: CreateUserRequest): Promise<User> => {
-  const user: User = {
-    id: nanoid(),
-    ...request,
-    createdAt: new Date().toISOString(),
-  };
-
-  const response = await apiClient.post<User>('/users', user);
-  return response.data;
+const createUser = async (
+	request: CreateUserRequest,
+): Promise<User> => {
+	const user: User = {
+		id: nanoid(),
+		...request,
+		createdAt: new Date().toISOString(),
+	};
+
+	const response = await apiClient.post<User>('/users', user);
+	return response.data;
 };
 ```
 
@@ -364,7 +371,8 @@ For 20+ common query patterns including joins and aggregations:
 Not just:
 
 ```markdown
-See [schema.md](references/schema.md) and [examples](references/query-examples.md).
+See [schema.md](references/schema.md) and
+[examples](references/query-examples.md).
 ```
 
 ---
@@ -405,27 +413,27 @@ Create scripts for:
 import { parseArgs } from 'node:util';
 
 async function main() {
-  const { values } = parseArgs({
-    options: {
-      verbose: { type: 'boolean', default: false },
-      file: { type: 'string' },
-      'check-all': { type: 'boolean', default: false },
-    },
-  });
-
-  try {
-    const result = await performOperation(values);
-    console.log(`✅ Success: ${result}`);
-    process.exit(0);
-  } catch (error) {
-    console.error(`❌ Error: ${error.message}`);
-    process.exit(1);
-  }
+	const { values } = parseArgs({
+		options: {
+			verbose: { type: 'boolean', default: false },
+			file: { type: 'string' },
+			'check-all': { type: 'boolean', default: false },
+		},
+	});
+
+	try {
+		const result = await performOperation(values);
+		console.log(`✅ Success: ${result}`);
+		process.exit(0);
+	} catch (error) {
+		console.error(`❌ Error: ${error.message}`);
+		process.exit(1);
+	}
 }
 
 async function performOperation(options) {
-  // Main logic here
-  return 'Operation completed';
+	// Main logic here
+	return 'Operation completed';
 }
 
 main();
@@ -545,7 +553,7 @@ Include authentication tokens in all API requests:
 
 ```typescript
 const response = await fetch(url, {
-  headers: { Authorization: `Bearer ${token}` },
+	headers: { Authorization: `Bearer ${token}` },
 });
 ```
 ````
@@ -604,6 +612,8 @@ Before finalizing a skill:
 
 ## Resources
 
-- [SKILLS-ARCHITECTURE.md](../../../docs/SKILLS-ARCHITECTURE.md) - System overview
-- [SKILL-DEVELOPMENT.md](../../../docs/SKILL-DEVELOPMENT.md) - Development workflow
+- [SKILLS-ARCHITECTURE.md](../../../docs/SKILLS-ARCHITECTURE.md) -
+  System overview
+- [SKILL-DEVELOPMENT.md](../../../docs/SKILL-DEVELOPMENT.md) -
+  Development workflow
 - [SKILL-EXAMPLES.md](../../../docs/SKILL-EXAMPLES.md) - Real examples

package/dist/skills/skill-creator/skill-creator/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: skill-creator
+description:
+  Design and create Claude Skills using progressive disclosure
+  principles. Use when building new skills, planning skill
+  architecture, or writing skill content.
+---
+
+# Skill Creator
+
+Principles and patterns for designing effective Claude Skills.
+
+## Quick Start
+
+Creating a minimal skill:
+
+1. Create directory: `.claude/skills/my-skill/`
+2. Create `SKILL.md` with frontmatter (name, description) and body
+3. Test in conversation
+4. Add references/ as content grows
+
+## When to Create a Skill
+
+Create a skill when you notice:
+
+- **Repeating context** across conversations (same schema, patterns,
+  rules)
+- **Domain expertise** needed repeatedly (API integration, framework
+  conventions)
+- **Project-specific knowledge** that Claude should know automatically
+
+Example: "I keep explaining this database schema" → Create a
+database-schema skill.
+
+## Skill Architecture
+
+Skills are directories with this structure:
+
+```
+my-skill/
+├── SKILL.md          # Required: Instructions + metadata
+├── references/       # Optional: Detailed documentation
+├── scripts/          # Optional: Executable operations
+└── assets/           # Optional: Templates, images, files
+```
+
+**SKILL.md** - Core instructions with YAML frontmatter (name,
+description) + markdown body
+
+**references/** - Detailed docs loaded only when Claude needs them
+(schemas, API docs, guides)
+
+**scripts/** - Deterministic operations Claude can execute without
+generating code (validation, generation)
+
+**assets/** - Files used directly in output without loading into
+context (templates, images)
+
+## Progressive Disclosure
+
+Skills load in 3 levels:
+
+**Level 1: Metadata** (~100 tokens, always loaded) - YAML frontmatter
+determines skill triggering
+
+**Level 2: Instructions** (<5k tokens, when triggered) - SKILL.md body
+with core patterns and links
+
+**Level 3: Resources** (unlimited, as needed) - references/ scripts/
+assets/ loaded only when used
+
+**Key principle**: Keep Levels 1 & 2 lean. Move details to Level 3.
+
+## Development Process
+
+1. **Recognize** - Notice repeated context or domain needs
+2. **Gather** - Collect 3-5 concrete examples of skill usage
+3. **Plan** - Decide what goes in SKILL.md vs references/ vs scripts/
+4. **Structure** - Create directory with SKILL.md and needed
+   subdirectories
+5. **Write** - Craft description, then SKILL.md body following
+   patterns
+6. **Enhance** - Add references, scripts, assets as needed
+7. **Iterate** - Test in conversations, refine based on actual usage
+
+## Writing Effective Content
+
+**Descriptions**: Include "Use when..." triggers, <200 chars optimal.
+Format: [Domain] + [Operations] + [Trigger keywords]
+
+**SKILL.md Body**: Target ~50 lines, max ~150. Structure: Quick
+Start + Core Patterns (3-5) + Links. Use imperative voice, concrete
+examples.
+
+**References**: Detailed docs with no size limit. Use descriptive
+filenames.
+
+## Common Patterns
+
+**Succeeds**: Domain expertise, concrete examples, keyword-rich
+descriptions, clear triggers, scripts for deterministic tasks
+
+**Fails**: Generic descriptions, bloated SKILL.md, second person
+voice, missing triggers, vague content
+
+See [skill-examples.md](references/skill-examples.md) for detailed
+patterns.
+
+## Implementation
+
+Skills can be created manually (mkdir, touch SKILL.md) or using tools
+like `claude-skills-cli`.
+
+For tool usage, see [cli-reference.md](references/cli-reference.md).
+
+## Reference Documentation
+
+For detailed guidance:
+
+- [anthropic-resources.md](references/anthropic-resources.md) -
+  Official Anthropic best practices
+- [writing-guide.md](references/writing-guide.md) - Voice, structure,
+  and code examples
+- [skill-examples.md](references/skill-examples.md) - Real-world
+  patterns and anti-patterns
+- [cli-reference.md](references/cli-reference.md) - Tool commands
+  (claude-skills-cli)
+- [cli-feedback.md](references/cli-feedback.md) - Real-world CLI usage
+  patterns
+
+## Notes
+
+- Skills are iterative - start minimal, refine through real usage
+- Description drives discovery - invest time in crafting it
+- Test in actual conversations to validate effectiveness
+- Progressive disclosure is key - resist urge to front-load everything
+
+<!--
+PROGRESSIVE DISCLOSURE:
+- This is Level 2 - principles and architecture only
+- Tool-specific details are in references/
+- Target: ~75 lines for optimal scannability
+-->