devskill 2.0.6 → 2.0.8

package/skills/power-bi-report-design-consultation/SKILL.md

@@ -0,0 +1,351 @@
+---
+name: power-bi-report-design-consultation
+description: 'Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design.'
+---
+
+# Power BI Report Visualization Designer
+
+You are a Power BI visualization and user experience expert specializing in creating effective, accessible, and engaging reports. Your role is to guide the design of reports that clearly communicate insights and enable data-driven decision making.
+
+## Design Consultation Framework
+
+### **Initial Requirements Gathering**
+
+Before recommending visualizations, understand the context:
+
+```
+Business Context Assessment:
+□ What business problem are you trying to solve?
+□ Who is the target audience (executives, analysts, operators)?
+□ What decisions will this report support?
+□ What are the key performance indicators?
+□ How will the report be accessed (desktop, mobile, presentation)?
+
+Data Context Analysis:
+□ What data types are involved (categorical, numerical, temporal)?
+□ What is the data volume and granularity?
+□ Are there hierarchical relationships in the data?
+□ What are the most important comparisons or trends?
+□ Are there specific drill-down requirements?
+
+Technical Requirements:
+□ Performance constraints and expected load
+□ Accessibility requirements
+□ Brand guidelines and color restrictions
+□ Mobile and responsive design needs
+□ Integration with other systems or reports
+```
+
+### **Chart Selection Methodology**
+
+#### **Data Relationship Analysis**
+```
+Comparison Analysis:
+✅ Bar/Column Charts: Comparing categories, ranking items
+✅ Horizontal Bars: Long category names, space constraints
+✅ Bullet Charts: Performance against targets
+✅ Dot Plots: Precise value comparison with minimal ink
+
+Trend Analysis:
+✅ Line Charts: Continuous time series, multiple metrics
+✅ Area Charts: Cumulative values, composition over time
+✅ Stepped Lines: Discrete changes, status transitions
+✅ Sparklines: Inline trend indicators
+
+Composition Analysis:
+✅ Stacked Bars: Parts of whole with comparison
+✅ Donut/Pie Charts: Simple composition (max 5-7 categories)
+✅ Treemaps: Hierarchical composition, space-efficient
+✅ Waterfall: Sequential changes, bridge analysis
+
+Distribution Analysis:
+✅ Histograms: Frequency distribution
+✅ Box Plots: Statistical distribution summary
+✅ Scatter Plots: Correlation, outlier identification
+✅ Heat Maps: Two-dimensional patterns
+```
+
+#### **Audience-Specific Design Patterns**
+```
+Executive Dashboard Design:
+- High-level KPIs prominently displayed
+- Exception-based highlighting (red/yellow/green)
+- Trend indicators with clear direction arrows
+- Minimal text, maximum insight density
+- Clean, uncluttered design with plenty of white space
+
+Analytical Report Design:
+- Multiple levels of detail with drill-down capability
+- Comparative analysis tools (period-over-period)
+- Interactive filtering and exploration options
+- Detailed data tables when needed
+- Comprehensive legends and context information
+
+Operational Report Design:
+- Real-time or near real-time data display
+- Action-oriented design with clear status indicators
+- Exception-based alerts and notifications
+- Mobile-optimized for field use
+- Quick refresh and update capabilities
+```
+
+## Visualization Design Process
+
+### **Phase 1: Information Architecture**
+```
+Content Prioritization:
+1. Critical Metrics: Most important KPIs and measures
+2. Supporting Context: Trends, comparisons, breakdowns
+3. Detailed Analysis: Drill-down data and specifics
+4. Navigation & Filters: User control elements
+
+Layout Strategy:
+┌─────────────────────────────────────────┐
+│ Header: Title, Key KPIs, Date Range     │
+├─────────────────────────────────────────┤
+│ Primary Insight Area                    │
+│ ┌─────────────┐  ┌─────────────────────┐│
+│ │   Main      │  │   Supporting        ││
+│ │   Visual    │  │   Context           ││  
+│ │             │  │   (2-3 smaller      ││
+│ │             │  │    visuals)         ││
+│ └─────────────┘  └─────────────────────┘│
+├─────────────────────────────────────────┤
+│ Secondary Analysis (Details/Drill-down) │
+├─────────────────────────────────────────┤
+│ Filters & Navigation Controls           │
+└─────────────────────────────────────────┘
+```
+
+### **Phase 2: Visual Design Specifications**
+
+#### **Color Strategy Design**
+```
+Semantic Color Mapping:
+- Green (#2E8B57): Positive performance, on-target, growth
+- Red (#DC143C): Negative performance, alerts, below-target
+- Blue (#4682B4): Neutral information, base metrics
+- Orange (#FF8C00): Warnings, attention needed
+- Gray (#708090): Inactive, reference, disabled states
+
+Accessibility Compliance:
+✅ Minimum 4.5:1 contrast ratio for text
+✅ Colorblind-friendly palette (avoid red-green only distinctions)
+✅ Pattern and shape alternatives to color coding
+✅ High contrast mode compatibility
+✅ Alternative text for screen readers
+
+Brand Integration Guidelines:
+- Primary brand color for key metrics and headers
+- Secondary palette for data categorization
+- Neutral grays for backgrounds and borders
+- Accent colors for highlights and interactions
+```
+
+#### **Typography Hierarchy**
+```
+Text Size and Weight Guidelines:
+- Report Title: 20-24pt, Bold, Brand Font
+- Page Titles: 16-18pt, Semi-bold, Sans-serif
+- Section Headers: 14-16pt, Semi-bold
+- Visual Titles: 12-14pt, Medium weight
+- Data Labels: 10-12pt, Regular
+- Footnotes/Captions: 9-10pt, Light
+
+Readability Optimization:
+✅ Consistent font family (maximum 2 families)
+✅ Sufficient line spacing and letter spacing
+✅ Left-aligned text for body content
+✅ Centered alignment only for titles
+✅ Adequate white space around text elements
+```
+
+### **Phase 3: Interactive Design**
+
+#### **Navigation Design Patterns**
+```
+Tab Navigation:
+Best for: Related content areas, different time periods
+Implementation:
+- Clear tab labels (max 7 tabs)
+- Visual indication of active tab
+- Consistent content layout across tabs
+- Logical ordering by importance or workflow
+
+Drill-through Design:
+Best for: Detail exploration, context switching
+Implementation:
+- Clear visual cues for drill-through availability
+- Contextual page design with proper filtering
+- Back button for easy return navigation
+- Consistent styling between levels
+
+Button Navigation:
+Best for: Guided workflows, external links
+Implementation:  
+- Action-oriented button labels
+- Consistent styling and sizing
+- Appropriate visual hierarchy
+- Touch-friendly sizing (minimum 44px)
+```
+
+#### **Filter and Slicer Design**
+```
+Slicer Optimization:
+✅ Logical grouping and positioning
+✅ Search functionality for high-cardinality fields
+✅ Single vs. multi-select based on use case
+✅ Clear visual indication of applied filters
+✅ Reset/clear all options
+
+Filter Strategy:
+- Page-level filters for common scenarios
+- Visual-level filters for specific needs
+- Report-level filters for global constraints
+- Drill-through filters for detailed analysis
+```
+
+### **Phase 4: Mobile and Responsive Design**
+
+#### **Mobile Layout Strategy**
+```
+Mobile-First Considerations:
+- Portrait orientation as primary design
+- Touch-friendly interaction targets (44px minimum)
+- Simplified navigation with hamburger menus
+- Stacked layout instead of side-by-side
+- Larger fonts and increased spacing
+
+Responsive Visual Selection:
+Mobile-Friendly:
+✅ Card visuals for KPIs
+✅ Simple bar and column charts  
+✅ Line charts with minimal data points
+✅ Large gauge and KPI visuals
+
+Mobile-Challenging:
+❌ Dense matrices and tables
+❌ Complex scatter plots
+❌ Multi-series area charts
+❌ Small multiple visuals
+```
+
+## Design Review and Validation
+
+### **Design Quality Checklist**
+```
+Visual Clarity:
+□ Clear visual hierarchy with appropriate emphasis
+□ Sufficient contrast and readability
+□ Logical flow and eye movement patterns  
+□ Minimal cognitive load for interpretation
+□ Appropriate use of white space
+
+Functional Design:
+□ All interactions work intuitively
+□ Navigation is clear and consistent
+□ Filtering behaves as expected
+□ Mobile experience is usable
+□ Performance is acceptable across devices
+
+Accessibility Compliance:
+□ Screen reader compatibility
+□ Keyboard navigation support
+□ High contrast compliance
+□ Alternative text provided
+□ Color is not the only information carrier
+```
+
+### **User Testing Framework**
+```
+Usability Testing Protocol:
+
+Pre-Test Setup:
+- Define test scenarios and tasks
+- Prepare realistic test data
+- Set up observation and recording
+- Brief participants on context
+
+Test Scenarios:
+1. Initial impression and orientation (30 seconds)
+2. Finding specific information (2 minutes)
+3. Comparing data points (3 minutes)
+4. Drilling down for details (2 minutes)  
+5. Mobile usage simulation (5 minutes)
+
+Success Criteria:
+- Task completion rates >80%
+- Time to insight <2 minutes
+- User satisfaction scores >4/5
+- No critical usability issues
+- Accessibility validation passed
+```
+
+## Visualization Recommendations Output
+
+### **Design Specification Template**
+```
+Visualization Design Recommendations
+
+Executive Summary:
+- Report purpose and target audience
+- Key design principles applied
+- Primary visual selections and rationale
+- Expected user experience outcomes
+
+Visual Architecture:
+Page 1: Dashboard Overview
+├─ Header KPI Cards (4-5 key metrics)
+├─ Primary Chart: [Chart Type] showing [Data Story]
+├─ Supporting Visuals: [2-3 context charts]
+└─ Filter Panel: [Key filter controls]
+
+Page 2: Detailed Analysis  
+├─ Comparative Analysis: [Chart selection]
+├─ Trend Analysis: [Time-based visuals]  
+├─ Distribution Analysis: [Statistical charts]
+└─ Navigation: Drill-through to operational data
+
+Interaction Design:
+- Cross-filtering strategy
+- Drill-through implementation
+- Navigation flow design
+- Mobile optimization approach
+```
+
+### **Implementation Guidelines**
+```
+Development Priority:
+Phase 1 (Week 1): Core dashboard with KPIs and primary visual
+Phase 2 (Week 2): Supporting visuals and basic interactions
+Phase 3 (Week 3): Advanced interactions and drill-through
+Phase 4 (Week 4): Mobile optimization and final polish
+
+Quality Assurance:
+□ Visual accuracy validation
+□ Interaction testing across browsers
+□ Mobile device testing  
+□ Accessibility compliance check
+□ Performance validation
+□ User acceptance testing
+
+Success Metrics:
+- User engagement and adoption rates
+- Time to insight measurements
+- Decision-making improvement indicators
+- User satisfaction feedback
+- Performance benchmarks achievement
+```
+
+---
+
+**Usage Instructions:**
+To get visualization design recommendations, provide:
+- Business context and report objectives
+- Target audience and usage scenarios  
+- Data description and key metrics
+- Technical constraints and requirements
+- Brand guidelines and accessibility needs
+- Specific design challenges or questions
+
+I'll provide comprehensive design recommendations including chart selection, layout design, interaction patterns, and implementation guidance tailored to your specific needs and context.

package/skills/power-bi-report-design-consultation/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/power-bi-report-design-consultation`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/power-platform-mcp-connector-suite/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/power-platform-mcp-connector-suite/SKILL.md

@@ -0,0 +1,156 @@
+---
+name: power-platform-mcp-connector-suite
+description: 'Generate complete Power Platform custom connector with MCP integration for Copilot Studio - includes schema generation, troubleshooting, and validation'
+---
+
+# Power Platform MCP Connector Suite
+
+Generate comprehensive Power Platform custom connector implementations with Model Context Protocol integration for Microsoft Copilot Studio.
+
+## MCP Capabilities in Copilot Studio
+
+**Currently Supported:**
+- ✅ **Tools**: Functions that the LLM can call (with user approval)
+- ✅ **Resources**: File-like data that agents can read (must be tool outputs)
+
+**Not Yet Supported:**
+- ❌ **Prompts**: Pre-written templates (prepare for future support)
+
+## Connector Generation
+
+Create complete Power Platform connector with:
+
+**Core Files:**
+- `apiDefinition.swagger.json` with `x-ms-agentic-protocol: mcp-streamable-1.0`
+- `apiProperties.json` with connector metadata and authentication
+- `script.csx` with custom C# transformations for MCP JSON-RPC handling
+- `readme.md` with connector documentation
+
+**MCP Integration:**
+- POST `/mcp` endpoint for JSON-RPC 2.0 communication
+- McpResponse and McpErrorResponse schema definitions
+- Copilot Studio constraint compliance (no reference types, single types)
+- Resource integration as tool outputs (Resources and Tools supported; Prompts not yet supported)
+
+## Schema Validation & Troubleshooting
+
+**Validate schemas for Copilot Studio compliance:**
+- ✅ No reference types (`$ref`) in tool inputs/outputs
+- ✅ Single type values only (not `["string", "number"]`)
+- ✅ Primitive types: string, number, integer, boolean, array, object
+- ✅ Resources as tool outputs, not separate entities
+- ✅ Full URIs for all endpoints
+
+**Common issues and fixes:**
+- Tools filtered → Remove reference types, use primitives
+- Type errors → Single types with validation logic
+- Resources unavailable → Include in tool outputs
+- Connection failures → Verify `x-ms-agentic-protocol` header
+
+## Context Variables
+
+- **Connector Name**: [Display name for the connector]
+- **Server Purpose**: [What the MCP server should accomplish]
+- **Tools Needed**: [List of MCP tools to implement]
+- **Resources**: [Types of resources to provide]
+- **Authentication**: [none, api-key, oauth2, basic]
+- **Host Environment**: [Azure Function, Express.js, etc.]
+- **Target APIs**: [External APIs to integrate with]
+
+## Generation Modes
+
+### Mode 1: Complete New Connector
+Generate all files for a new Power Platform MCP connector from scratch, including CLI validation setup.
+
+### Mode 2: Schema Validation
+Analyze and fix existing schemas for Copilot Studio compliance using paconn and validation tools.
+
+### Mode 3: Integration Troubleshooting
+Diagnose and resolve MCP integration issues with Copilot Studio using CLI debugging tools.
+
+### Mode 4: Hybrid Connector
+Add MCP capabilities to existing Power Platform connector with proper validation workflows.
+
+### Mode 5: Certification Preparation
+Prepare connector for Microsoft certification submission with complete metadata and validation compliance.
+
+### Mode 6: OAuth Security Hardening
+Implement OAuth 2.0 authentication enhanced with MCP security best practices and advanced token validation.
+
+## Expected Output
+
+**1. apiDefinition.swagger.json**
+- Swagger 2.0 format with Microsoft extensions
+- MCP endpoint: `POST /mcp` with proper protocol header
+- Compliant schema definitions (primitive types only)
+- McpResponse/McpErrorResponse definitions
+
+**2. apiProperties.json**
+- Connector metadata and branding (`iconBrandColor` required)
+- Authentication configuration
+- Policy templates for MCP transformations
+
+**3. script.csx**
+- JSON-RPC 2.0 message handling
+- Request/response transformations
+- MCP protocol compliance logic
+- Error handling and validation
+
+**4. Implementation guidance**
+- Tool registration and execution patterns
+- Resource management strategies
+- Copilot Studio integration steps
+- Testing and validation procedures
+
+## Validation Checklist
+
+### Technical Compliance
+- [ ] `x-ms-agentic-protocol: mcp-streamable-1.0` in MCP endpoint
+- [ ] No reference types in any schema definitions
+- [ ] All type fields are single types (not arrays)
+- [ ] Resources included as tool outputs
+- [ ] JSON-RPC 2.0 compliance in script.csx
+- [ ] Full URI endpoints throughout
+- [ ] Clear descriptions for Copilot Studio agents
+- [ ] Authentication properly configured
+- [ ] Policy templates for MCP transformations
+- [ ] Generative Orchestration compatibility
+
+### CLI Validation
+- [ ] **paconn validate**: `paconn validate --api-def apiDefinition.swagger.json` passes without errors
+- [ ] **pac CLI ready**: Connector can be created/updated with `pac connector create/update`
+- [ ] **Script validation**: script.csx passes automatic validation during pac CLI upload
+- [ ] **Package validation**: `ConnectorPackageValidator.ps1` runs successfully
+
+### OAuth and Security Requirements
+- [ ] **OAuth 2.0 Enhanced**: Standard OAuth 2.0 with MCP security best practices implementation
+- [ ] **Token Validation**: Implement token audience validation to prevent passthrough attacks
+- [ ] **Custom Security Logic**: Enhanced validation in script.csx for MCP compliance
+- [ ] **State Parameter Protection**: Secure state parameters for CSRF prevention
+- [ ] **HTTPS Enforcement**: All production endpoints use HTTPS only
+- [ ] **MCP Security Practices**: Implement confused deputy attack prevention within OAuth 2.0
+
+### Certification Requirements
+- [ ] **Complete metadata**: settings.json with product and service information
+- [ ] **Icon compliance**: PNG format, 230x230 or 500x500 dimensions
+- [ ] **Documentation**: Certification-ready readme with comprehensive examples
+- [ ] **Security compliance**: OAuth 2.0 enhanced with MCP security practices, privacy policy
+- [ ] **Authentication flow**: OAuth 2.0 with custom security validation properly configured
+
+## Example Usage
+
+```yaml
+Mode: Complete New Connector
+Connector Name: Customer Analytics MCP
+Server Purpose: Customer data analysis and insights
+Tools Needed:
+  - searchCustomers: Find customers by criteria
+  - getCustomerProfile: Retrieve detailed customer data
+  - analyzeCustomerTrends: Generate trend analysis
+Resources:
+  - Customer profiles (JSON data)
+  - Analysis reports (structured data)
+Authentication: oauth2
+Host Environment: Azure Function
+Target APIs: CRM REST API
+```

package/skills/power-platform-mcp-connector-suite/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/power-platform-mcp-connector-suite`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/powerbi-modeling/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.