devskill 2.0.7 → 2.0.8

package/skills/microsoft-skill-creator/references/skill-templates.md

@@ -0,0 +1,345 @@
+# Skill Templates
+
+Ready-to-use templates for different types of Microsoft technologies.
+
+## CLI Alternative for MCP Tools
+
+All templates below use MCP tool calls (e.g., `microsoft_docs_search`, `microsoft_docs_fetch`, `microsoft_code_sample_search`). If the Learn MCP server is not available, replace them with CLI equivalents:
+
+| MCP Tool | CLI Command |
+|----------|-------------|
+| `microsoft_docs_search(query: "...")` | `mslearn search "..."` |
+| `microsoft_code_sample_search(query: "...", language: "...")` | `mslearn code-search "..." --language ...` |
+| `microsoft_docs_fetch(url: "...")` | `mslearn fetch "..."` |
+
+Run directly with `npx @microsoft/learn-cli <command>` or install globally with `npm install -g @microsoft/learn-cli`.
+
+## Template 1: SDK/Library Skill
+
+For client libraries, SDKs, and programming frameworks.
+
+```markdown
+---
+name: {sdk-name}
+description: {What it does}. Use when agents need to {primary task} with {technology context}. Supports {languages/platforms}.
+---
+
+# {SDK Name}
+
+{One paragraph: what it is, why it exists, when to use it}
+
+## Installation
+
+{Package manager commands for supported languages}
+
+## Key Concepts
+
+{3-5 essential concepts, one paragraph each max}
+
+### {Concept 1}
+{Brief explanation}
+
+### {Concept 2}
+{Brief explanation}
+
+## Quick Start
+
+{Minimal working example - inline if <30 lines, otherwise reference sample_codes/}
+
+## Common Patterns
+
+### {Pattern 1: e.g., "Basic CRUD"}
+```{language}
+{code}
+```
+
+### {Pattern 2: e.g., "Error Handling"}
+```{language}
+{code}
+```
+
+## API Quick Reference
+
+| Class/Method | Purpose | Example |
+|--------------|---------|---------|
+| {name} | {what it does} | `{usage}` |
+
+For full API documentation:
+- `microsoft_docs_search(query="{sdk} {class} API reference")`
+- `microsoft_docs_fetch(url="{url}")`
+
+## Best Practices
+
+- **Do**: {recommendation}
+- **Do**: {recommendation}
+- **Avoid**: {anti-pattern}
+
+See [best-practices.md](references/best-practices.md) for detailed guidance.
+
+## Learn More
+
+| Topic | How to Find |
+|-------|-------------|
+| {Advanced topic 1} | `microsoft_docs_search(query="{sdk} {topic}")` |
+| {Advanced topic 2} | `microsoft_docs_fetch(url="{url}")` |
+| {Code examples} | `microsoft_code_sample_search(query="{sdk} {scenario}", language="{lang}")` |
+```
+
+---
+
+## Template 2: Azure Service Skill
+
+For Azure services and cloud resources.
+
+```markdown
+---
+name: {service-name}
+description: Work with {Azure Service}. Use when agents need to {primary capabilities}. Covers provisioning, configuration, and SDK usage.
+---
+
+# {Azure Service Name}
+
+{One paragraph: what the service does, primary use cases}
+
+## Overview
+
+- **Category**: {Compute/Storage/AI/Networking/etc.}
+- **Key capability**: {main value proposition}
+- **When to use**: {scenarios}
+
+## Getting Started
+
+### Prerequisites
+- Azure subscription
+- {Other requirements}
+
+### Provisioning
+{CLI/Portal/Bicep snippet for creating the resource}
+
+## SDK Usage ({Language})
+
+### Installation
+```
+{package install command}
+```
+
+### Authentication
+```{language}
+{auth code pattern}
+```
+
+### Basic Operations
+```{language}
+{CRUD or primary operations}
+```
+
+## Key Configurations
+
+| Setting | Purpose | Default |
+|---------|---------|---------|
+| {setting} | {what it controls} | {value} |
+
+## Pricing & Limits
+
+- **Pricing model**: {consumption/tier-based/etc.}
+- **Key limits**: {important quotas}
+
+For current pricing: `microsoft_docs_search(query="{service} pricing")`
+
+## Common Patterns
+
+### {Pattern 1}
+{Code or configuration}
+
+### {Pattern 2}
+{Code or configuration}
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| {Common error} | {Fix} |
+
+For more issues: `microsoft_docs_search(query="{service} troubleshoot {symptom}")`
+
+## Learn More
+
+| Topic | How to Find |
+|-------|-------------|
+| REST API | `microsoft_docs_fetch(url="{url}")` |
+| ARM/Bicep | `microsoft_docs_search(query="{service} bicep template")` |
+| Security | `microsoft_docs_search(query="{service} security best practices")` |
+```
+
+---
+
+## Template 3: Framework/Platform Skill
+
+For development frameworks and platforms (e.g., ASP.NET, MAUI, Blazor).
+
+```markdown
+---
+name: {framework-name}
+description: Build {type of apps} with {Framework}. Use when agents need to create, modify, or debug {framework} applications.
+---
+
+# {Framework Name}
+
+{One paragraph: what it is, what you build with it, why choose it}
+
+## Project Structure
+
+```
+{typical-project}/
+├── {folder}/     # {purpose}
+├── {file}        # {purpose}
+└── {file}        # {purpose}
+```
+
+## Getting Started
+
+### Create New Project
+```bash
+{CLI command to scaffold}
+```
+
+### Project Configuration
+{Key files to configure and what they control}
+
+## Core Concepts
+
+### {Concept 1: e.g., "Components"}
+{Explanation with minimal code example}
+
+### {Concept 2: e.g., "Routing"}
+{Explanation with minimal code example}
+
+### {Concept 3: e.g., "State Management"}
+{Explanation with minimal code example}
+
+## Common Patterns
+
+### {Pattern 1}
+```{language}
+{code}
+```
+
+### {Pattern 2}
+```{language}
+{code}
+```
+
+## Configuration Options
+
+| Setting | File | Purpose |
+|---------|------|---------|
+| {setting} | {file} | {what it does} |
+
+## Deployment
+
+{Brief deployment guidance or reference}
+
+For detailed deployment: `microsoft_docs_search(query="{framework} deploy {target}")`
+
+## Learn More
+
+| Topic | How to Find |
+|-------|-------------|
+| {Advanced feature} | `microsoft_docs_search(query="{framework} {feature}")` |
+| {Integration} | `microsoft_docs_fetch(url="{url}")` |
+| {Samples} | `microsoft_code_sample_search(query="{framework} {scenario}")` |
+```
+
+---
+
+## Template 4: API/Protocol Skill
+
+For APIs, protocols, and specifications (e.g., Microsoft Graph, OOXML).
+
+```markdown
+---
+name: {api-name}
+description: Interact with {API/Protocol}. Use when agents need to {primary operations}. Covers authentication, endpoints, and common operations.
+---
+
+# {API/Protocol Name}
+
+{One paragraph: what it provides access to, primary use cases}
+
+## Authentication
+
+{Auth method and code pattern}
+
+## Base Configuration
+
+- **Base URL**: `{url}`
+- **Version**: `{version}`
+- **Format**: {JSON/XML/etc.}
+
+## Common Endpoints/Operations
+
+### {Operation 1: e.g., "List Items"}
+```
+{HTTP method} {endpoint}
+```
+```{language}
+{SDK code}
+```
+
+### {Operation 2: e.g., "Create Item"}
+```
+{HTTP method} {endpoint}
+```
+```{language}
+{SDK code}
+```
+
+## Request/Response Patterns
+
+### Pagination
+{How to handle pagination}
+
+### Error Handling
+{Error format and common codes}
+
+## Quick Reference
+
+| Operation | Endpoint/Method | Notes |
+|-----------|-----------------|-------|
+| {op} | `{endpoint}` | {note} |
+
+## Permissions/Scopes
+
+| Operation | Required Permission |
+|-----------|---------------------|
+| {op} | `{permission}` |
+
+## Learn More
+
+| Topic | How to Find |
+|-------|-------------|
+| Full endpoint reference | `microsoft_docs_fetch(url="{url}")` |
+| Permissions | `microsoft_docs_search(query="{api} permissions {resource}")` |
+| SDKs | `microsoft_docs_search(query="{api} SDK {language}")` |
+```
+
+---
+
+## Choosing a Template
+
+| Technology Type | Template | Examples |
+|-----------------|----------|----------|
+| Client library, NuGet/npm package | SDK/Library | Semantic Kernel, Azure SDK, MSAL |
+| Azure resource | Azure Service | Cosmos DB, Azure Functions, App Service |
+| App development framework | Framework/Platform | ASP.NET Core, Blazor, MAUI |
+| REST API, protocol, specification | API/Protocol | Microsoft Graph, OOXML, FHIR |
+
+## Customization Guidelines
+
+Templates are starting points. Customize by:
+
+1. **Adding sections** for unique aspects of the technology
+2. **Removing sections** that don't apply
+3. **Adjusting depth** based on complexity (more concepts for complex tech)
+4. **Adding reference files** for detailed content that doesn't fit in SKILL.md
+5. **Adding sample_codes/** for working examples beyond inline snippets

package/skills/migrating-oracle-to-postgres-stored-procedures/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/migrating-oracle-to-postgres-stored-procedures/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: migrating-oracle-to-postgres-stored-procedures
+description: 'Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL. Translates Oracle-specific syntax, preserves method signatures and type-anchored parameters, leverages orafce where appropriate, and applies COLLATE "C" for Oracle-compatible text sorting. Use when converting Oracle stored procedures or functions to PostgreSQL equivalents during a database migration.'
+---
+
+# Migrating Stored Procedures from Oracle to PostgreSQL
+
+Translate Oracle PL/SQL stored procedures and functions to PostgreSQL PL/pgSQL equivalents.
+
+## Workflow
+
+```
+Progress:
+- [ ] Step 1: Read the Oracle source procedure
+- [ ] Step 2: Translate to PostgreSQL PL/pgSQL
+- [ ] Step 3: Write the migrated procedure to Postgres output directory
+```
+
+**Step 1: Read the Oracle source procedure**
+
+Read the Oracle stored procedure from `.github/oracle-to-postgres-migration/DDL/Oracle/Procedures and Functions/`. Consult the Oracle table/view definitions at `.github/oracle-to-postgres-migration/DDL/Oracle/Tables and Views/` for type resolution.
+
+**Step 2: Translate to PostgreSQL PL/pgSQL**
+
+Apply these translation rules:
+
+- Translate all Oracle-specific syntax to PostgreSQL equivalents.
+- Preserve original functionality and control flow logic.
+- Keep type-anchored input parameters (e.g., `PARAM_NAME IN table_name.column_name%TYPE`).
+- Use explicit types (`NUMERIC`, `VARCHAR`, `INTEGER`) for output parameters passed to other procedures — do not type-anchor these.
+- Do not alter method signatures.
+- Do not prefix object names with schema names unless already present in the Oracle source.
+- Leave exception handling and rollback logic unchanged.
+- Do not generate `COMMENT` or `GRANT` statements.
+- Use `COLLATE "C"` when ordering by text fields for Oracle-compatible sorting.
+- Leverage the `orafce` extension when it improves clarity or fidelity.
+
+Consult the PostgreSQL table/view definitions at `.github/oracle-to-postgres-migration/DDL/Postgres/Tables and Views/` for target schema details.
+
+**Step 3: Write the migrated procedure to Postgres output directory**
+
+Place each migrated procedure in its own file under `.github/oracle-to-postgres-migration/DDL/Postgres/Procedures and Functions/{PACKAGE_NAME_IF_APPLICABLE}/`. One procedure per file.

package/skills/migrating-oracle-to-postgres-stored-procedures/SYNC.md

@@ -0,0 +1,5 @@
+# Sync Info
+
+- **Source:** `vendor/awesome-copilot/skills/migrating-oracle-to-postgres-stored-procedures`
+- **Git SHA:** `23fb7006c132a0bba75b0e5af7a35cab11272812`
+- **Synced:** 2026-03-24

package/skills/mkdocs-translations/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/mkdocs-translations/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: mkdocs-translations
+description: 'Generate a language translation for a mkdocs documentation stack.'
+---
+
+# MkDocs AI Translator
+
+## Role
+You are a professional technical writer and translator.
+
+## Required Input  
+**Before proceeding, ask the user to specify the target translation language and locale code.**  
+Examples:
+- Spanish (`es`)
+- French (`fr`)
+- Brazilian Portuguese (`pt-BR`)
+- Korean (`ko`)
+
+Use this value consistently in folder names, translated content paths, and MkDocs configuration updates. Once confirmed, proceed with the instructions below.
+
+---
+
+## Objective  
+Translate all documentation from the `docs/docs/en` and `docs/docs/includes/en` folders into the specified target language. Preserve the original folder structure and all Markdown formatting.
+
+---
+
+## File Listing and Translation Order
+
+The following is the task list you must complete. Check each item off as it is done and report that to the user.
+
+- [ ] Begin by listing all files and subdirectories under `docs/docs/en`.
+- [ ] Then list all files and subdirectories under `docs/docs/includes/en`.
+- [ ] Translate **every file** in the list **one by one** in the order shown. Do not skip, reorder, or stop after a fixed number of files.
+- [ ] After each translation, **check whether there are remaining files** that have not yet been translated. If there are, **continue automatically** with the next file.
+- [ ] Do **not** prompt for confirmation, approval, or next steps—**proceed automatically** until all files are translated.
+- [ ] Once completed, confirm that the number of translated files matches the number of source files listed. If any files remain unprocessed, resume from where you left off.
+
+---
+
+## Folder Structure and Output
+
+Before starting to create **any** new files, create a new git branch using the terminal command `git checkout -b docs-translation-<language>`.
+
+- Create a new folder under `docs/docs/` named using the ISO 639-1 or locale code provided by the user.  
+  Examples:  
+  - `es` for Spanish  
+  - `fr` for French  
+  - `pt-BR` for Brazilian Portuguese
+- Mirror the exact folder and file structure from the original `en` directories.
+- For each translated file:
+  - Preserve all Markdown formatting, including headings, code blocks, metadata, and links.
+  - Maintain the original filename.
+  - Do **not** wrap the translated content in Markdown code blocks.
+  - Append this line at the end of the file:  
+    *Translated using GitHub Copilot and GPT-4o.*
+  - Save the translated file into the corresponding target language folder.
+
+---
+
+## Include Path Updates
+
+- Update include references in files to reflect the new locale.  
+  Example:  
+    `includes/en/introduction-event.md` → `includes/es/introduction-event.md`  
+  Replace `es` with the actual locale code provided by the user.
+
+---
+
+## MkDocs Configuration Update
+
+- [ ] Modify the `mkdocs.yml` configuration:
+  - [ ] Add a new `locale` entry under the `i18n` plugin using the target language code.
+  - [ ] Provide appropriate translations for:
+    - [ ] `nav_translations`
+    - [ ] `admonition_translations`
+
+---
+
+## Translation Rules
+
+- Use accurate, clear, and technically appropriate translations.
+- Always use computer industry-standard terminology.  
+  Example: prefer "Stack Tecnológica" over "Pila Tecnológica".
+
+**Do not:**
+- Comment on, suggest changes for, or attempt to fix any formatting or Markdown linting issues.  
+  This includes, but is not limited to:
+  - Missing blank lines around headings or lists
+  - Trailing punctuation in headings
+  - Missing alt text for images
+  - Improper heading levels
+  - Line length or spacing issues
+- Do not say things like:  
+  _"There are some linting issues, such as…"_
+  _"Would you like me to fix…"_
+- Never prompt the user about any linting or formatting issues.
+- Do not wait for confirmation before continuing.
+- Do not wrap the translated content or file in Markdown code blocks.
+
+---
+
+## Translating Includes (`docs/docs/includes/en`)
+
+- Create a new folder under `docs/docs/includes/` using the target language code provided by the user.
+- Translate each file using the same rules as above.
+- Maintain the same file and folder structure in the translated output.
+- Save each translated file in the appropriate target language folder.

package/skills/mkdocs-translations/SYNC.md

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

package/skills/model-recommendation/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.