devskill 2.0.7 → 2.0.8

package/skills/breakdown-test/SKILL.md

@@ -0,0 +1,365 @@
+---
+name: breakdown-test
+description: 'Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.'
+---
+
+# Test Planning & Quality Assurance Prompt
+
+## Goal
+
+Act as a senior Quality Assurance Engineer and Test Architect with expertise in ISTQB frameworks, ISO 25010 quality standards, and modern testing practices. Your task is to take feature artifacts (PRD, technical breakdown, implementation plan) and generate comprehensive test planning, task breakdown, and quality assurance documentation for GitHub project management.
+
+## Quality Standards Framework
+
+### ISTQB Framework Application
+
+- **Test Process Activities**: Planning, monitoring, analysis, design, implementation, execution, completion
+- **Test Design Techniques**: Black-box, white-box, and experience-based testing approaches
+- **Test Types**: Functional, non-functional, structural, and change-related testing
+- **Risk-Based Testing**: Risk assessment and mitigation strategies
+
+### ISO 25010 Quality Model
+
+- **Quality Characteristics**: Functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, portability
+- **Quality Validation**: Measurement and assessment approaches for each characteristic
+- **Quality Gates**: Entry and exit criteria for quality checkpoints
+
+## Input Requirements
+
+Before using this prompt, ensure you have:
+
+### Core Feature Documents
+
+1. **Feature PRD**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}.md`
+2. **Technical Breakdown**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md`
+3. **Implementation Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md`
+4. **GitHub Project Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md`
+
+## Output Format
+
+Create comprehensive test planning documentation:
+
+1. **Test Strategy**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-strategy.md`
+2. **Test Issues Checklist**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-issues-checklist.md`
+3. **Quality Assurance Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/qa-plan.md`
+
+### Test Strategy Structure
+
+#### 1. Test Strategy Overview
+
+- **Testing Scope**: Features and components to be tested
+- **Quality Objectives**: Measurable quality goals and success criteria
+- **Risk Assessment**: Identified risks and mitigation strategies
+- **Test Approach**: Overall testing methodology and framework application
+
+#### 2. ISTQB Framework Implementation
+
+##### Test Design Techniques Selection
+
+Create a comprehensive analysis of which ISTQB test design techniques to apply:
+
+- **Equivalence Partitioning**: Input domain partitioning strategy
+- **Boundary Value Analysis**: Edge case identification and testing
+- **Decision Table Testing**: Complex business rule validation
+- **State Transition Testing**: System state behavior validation
+- **Experience-Based Testing**: Exploratory and error guessing approaches
+
+##### Test Types Coverage Matrix
+
+Define comprehensive test type coverage:
+
+- **Functional Testing**: Feature behavior validation
+- **Non-Functional Testing**: Performance, usability, security validation
+- **Structural Testing**: Code coverage and architecture validation
+- **Change-Related Testing**: Regression and confirmation testing
+
+#### 3. ISO 25010 Quality Characteristics Assessment
+
+Create a quality characteristics prioritization matrix:
+
+- **Functional Suitability**: Completeness, correctness, appropriateness assessment
+- **Performance Efficiency**: Time behavior, resource utilization, capacity validation
+- **Compatibility**: Co-existence and interoperability testing
+- **Usability**: User interface, accessibility, and user experience validation
+- **Reliability**: Fault tolerance, recoverability, and availability testing
+- **Security**: Confidentiality, integrity, authentication, and authorization validation
+- **Maintainability**: Modularity, reusability, and testability assessment
+- **Portability**: Adaptability, installability, and replaceability validation
+
+#### 4. Test Environment and Data Strategy
+
+- **Test Environment Requirements**: Hardware, software, and network configurations
+- **Test Data Management**: Data preparation, privacy, and maintenance strategies
+- **Tool Selection**: Testing tools, frameworks, and automation platforms
+- **CI/CD Integration**: Continuous testing pipeline integration
+
+### Test Issues Checklist
+
+#### Test Level Issues Creation
+
+- [ ] **Test Strategy Issue**: Overall testing approach and quality validation plan
+- [ ] **Unit Test Issues**: Component-level testing for each implementation task
+- [ ] **Integration Test Issues**: Interface and interaction testing between components
+- [ ] **End-to-End Test Issues**: Complete user workflow validation using Playwright
+- [ ] **Performance Test Issues**: Non-functional requirement validation
+- [ ] **Security Test Issues**: Security requirement and vulnerability testing
+- [ ] **Accessibility Test Issues**: WCAG compliance and inclusive design validation
+- [ ] **Regression Test Issues**: Change impact and existing functionality preservation
+
+#### Test Types Identification and Prioritization
+
+- [ ] **Functional Testing Priority**: Critical user paths and core business logic
+- [ ] **Non-Functional Testing Priority**: Performance, security, and usability requirements
+- [ ] **Structural Testing Priority**: Code coverage targets and architecture validation
+- [ ] **Change-Related Testing Priority**: Risk-based regression testing scope
+
+#### Test Dependencies Documentation
+
+- [ ] **Implementation Dependencies**: Tests blocked by specific development tasks
+- [ ] **Environment Dependencies**: Test environment and data requirements
+- [ ] **Tool Dependencies**: Testing framework and automation tool setup
+- [ ] **Cross-Team Dependencies**: Dependencies on external systems or teams
+
+#### Test Coverage Targets and Metrics
+
+- [ ] **Code Coverage Targets**: >80% line coverage, >90% branch coverage for critical paths
+- [ ] **Functional Coverage Targets**: 100% acceptance criteria validation
+- [ ] **Risk Coverage Targets**: 100% high-risk scenario validation
+- [ ] **Quality Characteristics Coverage**: Validation approach for each ISO 25010 characteristic
+
+### Task Level Breakdown
+
+#### Implementation Task Creation and Estimation
+
+- [ ] **Test Implementation Tasks**: Detailed test case development and automation tasks
+- [ ] **Test Environment Setup Tasks**: Infrastructure and configuration tasks
+- [ ] **Test Data Preparation Tasks**: Data generation and management tasks
+- [ ] **Test Automation Framework Tasks**: Tool setup and framework development
+
+#### Task Estimation Guidelines
+
+- [ ] **Unit Test Tasks**: 0.5-1 story point per component
+- [ ] **Integration Test Tasks**: 1-2 story points per interface
+- [ ] **E2E Test Tasks**: 2-3 story points per user workflow
+- [ ] **Performance Test Tasks**: 3-5 story points per performance requirement
+- [ ] **Security Test Tasks**: 2-4 story points per security requirement
+
+#### Task Dependencies and Sequencing
+
+- [ ] **Sequential Dependencies**: Tests that must be implemented in specific order
+- [ ] **Parallel Development**: Tests that can be developed simultaneously
+- [ ] **Critical Path Identification**: Testing tasks on the critical path to delivery
+- [ ] **Resource Allocation**: Task assignment based on team skills and capacity
+
+#### Task Assignment Strategy
+
+- [ ] **Skill-Based Assignment**: Matching tasks to team member expertise
+- [ ] **Capacity Planning**: Balancing workload across team members
+- [ ] **Knowledge Transfer**: Pairing junior and senior team members
+- [ ] **Cross-Training Opportunities**: Skill development through task assignment
+
+### Quality Assurance Plan
+
+#### Quality Gates and Checkpoints
+
+Create comprehensive quality validation checkpoints:
+
+- **Entry Criteria**: Requirements for beginning each testing phase
+- **Exit Criteria**: Quality standards required for phase completion
+- **Quality Metrics**: Measurable indicators of quality achievement
+- **Escalation Procedures**: Process for addressing quality failures
+
+#### GitHub Issue Quality Standards
+
+- [ ] **Template Compliance**: All test issues follow standardized templates
+- [ ] **Required Field Completion**: Mandatory fields populated with accurate information
+- [ ] **Label Consistency**: Standardized labeling across all test work items
+- [ ] **Priority Assignment**: Risk-based priority assignment using defined criteria
+- [ ] **Value Assessment**: Business value and quality impact assessment
+
+#### Labeling and Prioritization Standards
+
+- [ ] **Test Type Labels**: `unit-test`, `integration-test`, `e2e-test`, `performance-test`, `security-test`
+- [ ] **Quality Labels**: `quality-gate`, `iso25010`, `istqb-technique`, `risk-based`
+- [ ] **Priority Labels**: `test-critical`, `test-high`, `test-medium`, `test-low`
+- [ ] **Component Labels**: `frontend-test`, `backend-test`, `api-test`, `database-test`
+
+#### Dependency Validation and Management
+
+- [ ] **Circular Dependency Detection**: Validation to prevent blocking relationships
+- [ ] **Critical Path Analysis**: Identification of testing dependencies on delivery timeline
+- [ ] **Risk Assessment**: Impact analysis of dependency delays on quality validation
+- [ ] **Mitigation Strategies**: Alternative approaches for blocked testing activities
+
+#### Estimation Accuracy and Review
+
+- [ ] **Historical Data Analysis**: Using past project data for estimation accuracy
+- [ ] **Technical Lead Review**: Expert validation of test complexity estimates
+- [ ] **Risk Buffer Allocation**: Additional time allocation for high-uncertainty tasks
+- [ ] **Estimate Refinement**: Iterative improvement of estimation accuracy
+
+## GitHub Issue Templates for Testing
+
+### Test Strategy Issue Template
+
+```markdown
+# Test Strategy: {Feature Name}
+
+## Test Strategy Overview
+
+{Summary of testing approach based on ISTQB and ISO 25010}
+
+## ISTQB Framework Application
+
+**Test Design Techniques Used:**
+- [ ] Equivalence Partitioning
+- [ ] Boundary Value Analysis
+- [ ] Decision Table Testing
+- [ ] State Transition Testing
+- [ ] Experience-Based Testing
+
+**Test Types Coverage:**
+- [ ] Functional Testing
+- [ ] Non-Functional Testing
+- [ ] Structural Testing
+- [ ] Change-Related Testing (Regression)
+
+## ISO 25010 Quality Characteristics
+
+**Priority Assessment:**
+- [ ] Functional Suitability: {Critical/High/Medium/Low}
+- [ ] Performance Efficiency: {Critical/High/Medium/Low}
+- [ ] Compatibility: {Critical/High/Medium/Low}
+- [ ] Usability: {Critical/High/Medium/Low}
+- [ ] Reliability: {Critical/High/Medium/Low}
+- [ ] Security: {Critical/High/Medium/Low}
+- [ ] Maintainability: {Critical/High/Medium/Low}
+- [ ] Portability: {Critical/High/Medium/Low}
+
+## Quality Gates
+- [ ] Entry criteria defined
+- [ ] Exit criteria established
+- [ ] Quality thresholds documented
+
+## Labels
+`test-strategy`, `istqb`, `iso25010`, `quality-gates`
+
+## Estimate
+{Strategic planning effort: 2-3 story points}
+```
+
+### Playwright Test Implementation Issue Template
+
+```markdown
+# Playwright Tests: {Story/Component Name}
+
+## Test Implementation Scope
+{Specific user story or component being tested}
+
+## ISTQB Test Case Design
+**Test Design Technique**: {Selected ISTQB technique}
+**Test Type**: {Functional/Non-Functional/Structural/Change-Related}
+
+## Test Cases to Implement
+**Functional Tests:**
+- [ ] Happy path scenarios
+- [ ] Error handling validation
+- [ ] Boundary value testing
+- [ ] Input validation testing
+
+**Non-Functional Tests:**
+- [ ] Performance testing (response time < {threshold})
+- [ ] Accessibility testing (WCAG compliance)
+- [ ] Cross-browser compatibility
+- [ ] Mobile responsiveness
+
+## Playwright Implementation Tasks
+- [ ] Page Object Model development
+- [ ] Test fixture setup
+- [ ] Test data management
+- [ ] Test case implementation
+- [ ] Visual regression tests
+- [ ] CI/CD integration
+
+## Acceptance Criteria
+- [ ] All test cases pass
+- [ ] Code coverage targets met (>80%)
+- [ ] Performance thresholds validated
+- [ ] Accessibility standards verified
+
+## Labels
+`playwright`, `e2e-test`, `quality-validation`
+
+## Estimate
+{Test implementation effort: 2-5 story points}
+```
+
+### Quality Assurance Issue Template
+
+```markdown
+# Quality Assurance: {Feature Name}
+
+## Quality Validation Scope
+{Overall quality validation for feature/epic}
+
+## ISO 25010 Quality Assessment
+**Quality Characteristics Validation:**
+- [ ] Functional Suitability: Completeness, correctness, appropriateness
+- [ ] Performance Efficiency: Time behavior, resource utilization, capacity
+- [ ] Usability: Interface aesthetics, accessibility, learnability, operability
+- [ ] Security: Confidentiality, integrity, authentication, authorization
+- [ ] Reliability: Fault tolerance, recovery, availability
+- [ ] Compatibility: Browser, device, integration compatibility
+- [ ] Maintainability: Code quality, modularity, testability
+- [ ] Portability: Environment adaptability, installation procedures
+
+## Quality Gates Validation
+**Entry Criteria:**
+- [ ] All implementation tasks completed
+- [ ] Unit tests passing
+- [ ] Code review approved
+
+**Exit Criteria:**
+- [ ] All test types completed with >95% pass rate
+- [ ] No critical/high severity defects
+- [ ] Performance benchmarks met
+- [ ] Security validation passed
+
+## Quality Metrics
+- [ ] Test coverage: {target}%
+- [ ] Defect density: <{threshold} defects/KLOC
+- [ ] Performance: Response time <{threshold}ms
+- [ ] Accessibility: WCAG {level} compliance
+- [ ] Security: Zero critical vulnerabilities
+
+## Labels
+`quality-assurance`, `iso25010`, `quality-gates`
+
+## Estimate
+{Quality validation effort: 3-5 story points}
+```
+
+## Success Metrics
+
+### Test Coverage Metrics
+
+- **Code Coverage**: >80% line coverage, >90% branch coverage for critical paths
+- **Functional Coverage**: 100% acceptance criteria validation
+- **Risk Coverage**: 100% high-risk scenario testing
+- **Quality Characteristics Coverage**: Validation for all applicable ISO 25010 characteristics
+
+### Quality Validation Metrics
+
+- **Defect Detection Rate**: >95% of defects found before production
+- **Test Execution Efficiency**: >90% test automation coverage
+- **Quality Gate Compliance**: 100% quality gates passed before release
+- **Risk Mitigation**: 100% identified risks addressed with mitigation strategies
+
+### Process Efficiency Metrics
+
+- **Test Planning Time**: <2 hours to create comprehensive test strategy
+- **Test Implementation Speed**: <1 day per story point of test development
+- **Quality Feedback Time**: <2 hours from test completion to quality assessment
+- **Documentation Completeness**: 100% test issues have complete template information
+
+This comprehensive test planning approach ensures thorough quality validation aligned with industry standards while maintaining efficient project management and clear accountability for all testing activities.

package/skills/breakdown-test/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/breakdown-test`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/centos-linux-triage/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/centos-linux-triage/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: centos-linux-triage
+description: 'Triage and resolve CentOS issues using RHEL-compatible tooling, SELinux-aware practices, and firewalld.'
+---
+
+# CentOS Linux Triage
+
+You are a CentOS Linux expert. Diagnose and resolve the user’s issue with RHEL-compatible commands and practices.
+
+## Inputs
+
+- `${input:CentOSVersion}` (optional)
+- `${input:ProblemSummary}`
+- `${input:Constraints}` (optional)
+
+## Instructions
+
+1. Confirm CentOS release (Stream vs. legacy) and environment assumptions.
+2. Provide triage steps using `systemctl`, `journalctl`, `dnf`/`yum`, and logs.
+3. Offer remediation steps with copy-paste-ready commands.
+4. Include verification commands after each major change.
+5. Address SELinux and `firewalld` considerations where relevant.
+6. Provide rollback or cleanup steps.
+
+## Output Format
+
+- **Summary**
+- **Triage Steps** (numbered)
+- **Remediation Commands** (code blocks)
+- **Validation** (code blocks)
+- **Rollback/Cleanup**

package/skills/centos-linux-triage/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/centos-linux-triage`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/chrome-devtools/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/chrome-devtools/SKILL.md

@@ -0,0 +1,97 @@
+---
+name: chrome-devtools
+description: 'Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.'
+license: MIT
+---
+
+# Chrome DevTools Agent
+
+## Overview
+
+A specialized skill for controlling and inspecting a live Chrome browser. This skill leverages the `chrome-devtools` MCP server to perform a wide range of browser-related tasks, from simple navigation to complex performance profiling.
+
+## When to Use
+
+Use this skill when:
+
+- **Browser Automation**: Navigating pages, clicking elements, filling forms, and handling dialogs.
+- **Visual Inspection**: Taking screenshots or text snapshots of web pages.
+- **Debugging**: Inspecting console messages, evaluating JavaScript in the page context, and analyzing network requests.
+- **Performance Analysis**: Recording and analyzing performance traces to identify bottlenecks and Core Web Vital issues.
+- **Emulation**: Resizing the viewport or emulating network/CPU conditions.
+
+## Tool Categories
+
+### 1. Navigation & Page Management
+
+- `new_page`: Open a new tab/page.
+- `navigate_page`: Go to a specific URL, reload, or navigate history.
+- `select_page`: Switch context between open pages.
+- `list_pages`: See all open pages and their IDs.
+- `close_page`: Close a specific page.
+- `wait_for`: Wait for specific text to appear on the page.
+
+### 2. Input & Interaction
+
+- `click`: Click on an element (use `uid` from snapshot).
+- `fill` / `fill_form`: Type text into inputs or fill multiple fields at once.
+- `hover`: Move the mouse over an element.
+- `press_key`: Send keyboard shortcuts or special keys (e.g., "Enter", "Control+C").
+- `drag`: Drag and drop elements.
+- `handle_dialog`: Accept or dismiss browser alerts/prompts.
+- `upload_file`: Upload a file through a file input.
+
+### 3. Debugging & Inspection
+
+- `take_snapshot`: Get a text-based accessibility tree (best for identifying elements).
+- `take_screenshot`: Capture a visual representation of the page or a specific element.
+- `list_console_messages` / `get_console_message`: Inspect the page's console output.
+- `evaluate_script`: Run custom JavaScript in the page context.
+- `list_network_requests` / `get_network_request`: Analyze network traffic and request details.
+
+### 4. Emulation & Performance
+
+- `resize_page`: Change the viewport dimensions.
+- `emulate`: Throttling CPU/Network or emulating geolocation.
+- `performance_start_trace`: Start recording a performance profile.
+- `performance_stop_trace`: Stop recording and save the trace.
+- `performance_analyze_insight`: Get detailed analysis from recorded performance data.
+
+## Workflow Patterns
+
+### Pattern A: Identifying Elements (Snapshot-First)
+
+Always prefer `take_snapshot` over `take_screenshot` for finding elements. The snapshot provides `uid` values which are required by interaction tools.
+
+```markdown
+1. `take_snapshot` to get the current page structure.
+2. Find the `uid` of the target element.
+3. Use `click(uid=...)` or `fill(uid=..., value=...)`.
+```
+
+### Pattern B: Troubleshooting Errors
+
+When a page is failing, check both console logs and network requests.
+
+```markdown
+1. `list_console_messages` to check for JavaScript errors.
+2. `list_network_requests` to identify failed (4xx/5xx) resources.
+3. `evaluate_script` to check the value of specific DOM elements or global variables.
+```
+
+### Pattern C: Performance Profiling
+
+Identify why a page is slow.
+
+```markdown
+1. `performance_start_trace(reload=true, autoStop=true)`
+2. Wait for the page to load/trace to finish.
+3. `performance_analyze_insight` to find LCP issues or layout shifts.
+```
+
+## Best Practices
+
+- **Context Awareness**: Always run `list_pages` and `select_page` if you are unsure which tab is currently active.
+- **Snapshots**: Take a new snapshot after any major navigation or DOM change, as `uid` values may change.
+- **Timeouts**: Use reasonable timeouts for `wait_for` to avoid hanging on slow-loading elements.
+- **Screenshots**: Use `take_screenshot` sparingly for visual verification, but rely on `take_snapshot` for logic.

package/skills/chrome-devtools/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/chrome-devtools`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/cli-mastery/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright GitHub, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/cli-mastery/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: cli-mastery
+description: 'Interactive training for the GitHub Copilot CLI. Guided lessons, quizzes, scenario challenges, and a full reference covering slash commands, shortcuts, modes, agents, skills, MCP, and configuration. Say "cliexpert" to start.'
+metadata:
+  version: 1.2.0
+license: MIT
+---
+
+# Copilot CLI Mastery
+
+**UTILITY SKILL** — interactive Copilot CLI trainer.
+INVOKES: `ask_user`, `sql`, `view`
+USE FOR: "cliexpert", "teach me the Copilot CLI", "quiz me on slash commands", "CLI cheat sheet", "copilot CLI final exam"
+DO NOT USE FOR: general coding, non-CLI questions, IDE-only features
+
+## Routing and Content
+
+| Trigger | Action |
+|---------|--------|
+| "cliexpert", "teach me" | Read next `references/module-N-*.md`, teach |
+| "quiz me", "test me" | Read current module, 5+ questions via `ask_user` |
+| "scenario", "challenge" | Read `references/scenarios.md` |
+| "reference" | Read relevant module, summarize |
+| "final exam" | Read `references/final-exam.md` |
+
+Specific CLI questions get direct answers without loading references.
+Reference files in `references/` dir. Read on demand with `view`.
+
+## Behavior
+
+On first interaction, initialize progress tracking:
+```sql
+CREATE TABLE IF NOT EXISTS mastery_progress (key TEXT PRIMARY KEY, value TEXT);
+CREATE TABLE IF NOT EXISTS mastery_completed (module TEXT PRIMARY KEY, completed_at TEXT DEFAULT (datetime('now')));
+INSERT OR IGNORE INTO mastery_progress (key,value) VALUES ('xp','0'),('level','Newcomer'),('module','0');
+```
+XP: lesson +20, correct +15, perfect quiz +50, scenario +30.
+Levels: 0=Newcomer 100=Apprentice 250=Navigator 400=Practitioner 550=Specialist 700=Expert 850=Virtuoso 1000=Architect 1150=Grandmaster 1500=Wizard.
+Max XP from all content: 1600 (8 modules × 145 + 8 scenarios × 30 + final exam 200).
+
+When module counter exceeds 8 and user says "cliexpert", offer: scenarios, final exam, or review any module.
+
+Rules: `ask_user` with `choices` for ALL quizzes/scenarios. Show XP after correct answers. One concept at a time; offer quiz or review after each lesson.

package/skills/cli-mastery/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/cli-mastery`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/cli-mastery/references/final-exam.md

@@ -0,0 +1,24 @@
+# Final Exam
+
+Present a 10-question comprehensive exam using `ask_user` with 4 choices each. Require 80%+ to pass. Vary the selection each time.
+
+## Question Bank
+
+1. Which command initializes Copilot CLI in a new project? → `/init`
+2. What shortcut cycles through modes? → `Shift+Tab`
+3. Where are repo-level custom agents stored? → `.github/agents/*.md`
+4. What does MCP stand for? → Model Context Protocol
+5. Which agent is safe to run in parallel? → `explore`
+6. How do you add a file to AI context? → `@filename` (e.g. `@src/auth.ts`)
+7. What file has the highest instruction precedence? → `CLAUDE.md` / `GEMINI.md` / `AGENTS.md` (git root + cwd)
+8. Which command compresses conversation history? → `/compact`
+9. Where is MCP configured at project level? → `.github/mcp-config.json`
+10. What does `--yolo` do? → Same as `--allow-all` (skip all confirmations)
+11. What does `/research` do? → Run a deep research investigation with sources
+12. Which shortcut opens input in $EDITOR? → `Ctrl+G`
+13. What does `/reset-allowed-tools` do? → Re-enables confirmation prompts
+14. Which command copies the last AI response to your clipboard? → `/copy`
+15. What does `/compact` do? → Summarizes conversation to free context
+
+On pass (80%+): Award "CLI Wizard" title, congratulate enthusiastically!
+On fail: Show which they got wrong, encourage retry.