/engineer-skill-creator

name: engineer-skill-creator
description: Transform extracted engineer expertise into an actionable skill with progressive disclosure, allowing agents to find and apply relevant patterns for specific tasks.

Engineer Skill Creator

Transform extracted engineer profiles into ready-to-use skills with progressive disclosure, enabling AI agents to efficiently find and apply the right expertise for any coding task.

What This Skill Does

Takes the output from **engineer-expertise-extractor** and creates a structured, queryable skill that:

• **Organizes expertise by task type** - Find relevant patterns quickly
• **Uses progressive disclosure** - Show only what's needed for current task
• **Provides contextual examples** - Real code samples for specific scenarios
• **Guides agents intelligently** - Help find the right expertise at the right time
• **Enables task-specific queries** - "How would they handle authentication?"

The Two-Step Process

Step 1: Extract (engineer-expertise-extractor)

./extract_engineer.sh senior_dev
# Output: engineer_profiles/senior_dev/

Step 2: Create Skill (THIS SKILL)

./create_expert_skill.sh senior_dev
# Output: expert-skills/senior-dev-mentor/

**Result:** A ready-to-use skill that agents can query for specific guidance.

Why Progressive Disclosure Matters

**Without progressive disclosure:**

• Agent gets all expertise at once (overwhelming)
• Hard to find relevant information
• Context limits reached quickly
• Inefficient and slow

**With progressive disclosure:**

• Agent asks specific question
• Gets only relevant expertise
• Focused, actionable guidance
• Efficient use of context
• Faster, better results

Output Structure

When you create a skill from an engineer profile, you get:

expert-skills/
└── [engineer-name]-mentor/
    ├── SKILL.md (skill documentation)
    ├── query_expertise.sh (interactive query tool)
    ├── expertise/
    │   ├── by_task/
    │   │   ├── authentication.md
    │   │   ├── api_design.md
    │   │   ├── database_design.md
    │   │   ├── error_handling.md
    │   │   └── testing.md
    │   ├── by_language/
    │   │   ├── typescript.md
    │   │   ├── python.md
    │   │   └── go.md
    │   ├── by_pattern/
    │   │   ├── dependency_injection.md
    │   │   ├── repository_pattern.md
    │   │   └── factory_pattern.md
    │   └── quick_reference/
    │       ├── coding_style.md
    │       ├── naming_conventions.md
    │       └── best_practices.md
    └── examples/
        ├── authentication_service.ts
        ├── api_controller.ts
        └── test_example.spec.ts

Progressive Disclosure System

Query by Task

**Agent asks:** "How would they implement user authentication?"

**Skill provides:** 1. Relevant patterns from `by_task/authentication.md` 2. Code examples from their auth PRs 3. Their testing approach for auth 4. Security considerations they use 5. Related best practices

**NOT provided (yet):**

• Unrelated patterns
• Database design details
• Payment processing approach
• Everything else

Query by Language

**Agent asks:** "Show me their TypeScript coding style"

**Skill provides:** 1. TypeScript-specific conventions 2. Type usage patterns 3. Interface design approach 4. Error handling in TS 5. Real TS examples

Query by Pattern

**Agent asks:** "How do they implement dependency injection?"

**Skill provides:** 1. DI pattern from their code 2. Constructor injection examples 3. IoC container setup 4. Testing with DI 5. When they use it vs when they don't

Skill Usage by Agents

Basic Query

"Using the skill expert-skills/senior-dev-mentor/, show me how to
implement authentication"

**Skill responds with:**

• Authentication patterns they use
• Real code examples
• Testing approach
• Security practices
• Step-by-step guidance

Language-Specific Query

"Using expert-skills/senior-dev-mentor/, write a TypeScript service
following their style"

**Skill provides:**

• TypeScript coding conventions
• Class structure patterns
• Type definitions approach
• Import organization
• Testing patterns for services

Pattern-Specific Query

"Using expert-skills/senior-dev-mentor/, implement the repository
pattern as they would"

**Skill provides:**

• Their repository pattern implementation
• Interface definitions
• Concrete implementation example
• Testing approach
• When to use this pattern

Created Skill Features

1. Task-Based Navigation

Expertise organized by common development tasks:

• Authentication & Authorization
• API Design
• Database Design
• Error Handling
• Testing Strategies
• Performance Optimization
• Security Practices
• Code Review Guidelines

2. Language-Specific Guidance

Separate docs for each language they use:

• Naming conventions per language
• Language-specific patterns
• Idiomatic code examples
• Framework preferences

3. Pattern Library

Design patterns they commonly use:

• When to apply each pattern
• Implementation examples
• Testing approach
• Common pitfalls to avoid

4. Quick Reference

Fast access to essentials:

• Coding style at a glance
• Naming conventions cheat sheet
• Common commands/snippets
• Review checklist

5. Interactive Query Tool

Script that helps find expertise:

./query_expertise.sh

What are you working on?
1) Authentication
2) API Design
3) Database
4) Testing
5) Custom query

Select: 1

=== Authentication Expertise ===

[Shows relevant patterns, examples, best practices]

How Skills Are Created

Input

Engineer profile from extractor:

engineer_profiles/senior_dev/
├── coding_style/
├── patterns/
├── best_practices/
├── architecture/
├── code_review/
└── examples/

Process

1. **Analyze profile structure** 2. **Categorize by task** - Group related expertise 3. **Extract examples** - Pull relevant code samples 4. **Create navigation** - Build progressive disclosure system 5. **Generate queries** - Create query tool 6. **Package skill** - R