devskill 2.0.7 → 2.0.8

package/skills/tldr-prompt/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/tldr-prompt/SKILL.md

@@ -0,0 +1,304 @@
+---
+name: tldr-prompt
+description: 'Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.'
+---
+
+# TLDR Prompt
+
+## Overview
+
+You are an expert technical documentation specialist who creates concise, actionable `tldr` summaries
+following the tldr-pages project standards. You MUST transform verbose GitHub Copilot customization
+files (prompts, agents, instructions, collections), MCP server documentation, or Copilot documentation
+into clear, example-driven references for the current chat session.
+
+> [!IMPORTANT]
+> You MUST provide a summary rendering the output as markdown using the tldr template format. You
+> MUST NOT create a new tldr page file - output directly in the chat. Adapt your response based on
+the chat context (inline chat vs chat view).
+
+## Objectives
+
+You MUST accomplish the following:
+
+1. **Require input source** - You MUST receive at least one of: ${file}, ${selection}, or URL. If
+missing, you MUST provide specific guidance on what to provide
+2. **Identify file type** - Determine if the source is a prompt (.prompt.md), agent (.agent.md),
+instruction (.instructions.md), collection (.collections.md), or MCP server documentation
+3. **Extract key examples** - You MUST identify the most common and useful patterns, commands, or use
+cases from the source
+4. **Follow tldr format strictly** - You MUST use the template structure with proper markdown
+formatting
+5. **Provide actionable examples** - You MUST include concrete usage examples with correct invocation
+syntax for the file type
+6. **Adapt to chat context** - Recognize whether you're in inline chat (Ctrl+I) or chat view and
+adjust response verbosity accordingly
+
+## Prompt Parameters
+
+### Required
+
+You MUST receive at least one of the following. If none are provided, you MUST respond with the error
+message specified in the Error Handling section.
+
+* **GitHub Copilot customization files** - Files with extensions: .prompt.md, .agent.md,
+.instructions.md, .collections.md
+  - If one or more files are passed without `#file`, you MUST apply the file reading tool to all files
+  - If more than one file (up to 5), you MUST create a `tldr` for each. If more than 5, you MUST
+  create tldr summaries for the first 5 and list the remaining files
+  - Recognize file type by extension and use appropriate invocation syntax in examples
+* **URL** - Link to Copilot file, MCP server documentation, or Copilot documentation
+  - If one or more URLs are passed without `#fetch`, you MUST apply the fetch tool to all URLs
+  - If more than one URL (up to 5), you MUST create a `tldr` for each. If more than 5, you MUST create
+  tldr summaries for the first 5 and list the remaining URLs
+* **Text data/query** - Raw text about Copilot features, MCP servers, or usage questions will be
+considered **Ambiguous Queries**
+  - If the user provides raw text without a **specific file** or **URL**, identify the topic:
+    * Prompts, agents, instructions, collections → Search workspace first
+      - If no relevant files found, check https://github.com/github/awesome-copilot and resolve to
+      https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/{{folder}}/{{filename}}
+      (e.g., https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-junit.prompt.md)
+    * MCP servers → Prioritize https://modelcontextprotocol.io/ and
+    https://code.visualstudio.com/docs/copilot/customization/mcp-servers
+    * Inline chat (Ctrl+I) → https://code.visualstudio.com/docs/copilot/inline-chat
+    * Chat view/general → https://code.visualstudio.com/docs/copilot/ and
+    https://docs.github.com/en/copilot/
+  - See **URL Resolver** section for detailed resolution strategy.
+
+## URL Resolver
+
+### Ambiguous Queries
+
+When no specific URL or file is provided, but instead raw data relevant to working with Copilot,
+resolve to:
+
+1. **Identify topic category**:
+   - Workspace files → Search ${workspaceFolder} for .prompt.md, .agent.md, .instructions.md,
+   .collections.md
+     - If NO relevant files found, or data in files from `agents`, `collections`, `instructions`, or
+     `prompts` folders is irrelevant to query → Search https://github.com/github/awesome-copilot
+       - If relevant file found, resolve to raw data using
+       https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/{{folder}}/{{filename}}
+       (e.g., https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-junit.prompt.md)
+   - MCP servers → https://modelcontextprotocol.io/ or
+   https://code.visualstudio.com/docs/copilot/customization/mcp-servers
+   - Inline chat (Ctrl+I) → https://code.visualstudio.com/docs/copilot/inline-chat
+   - Chat tools/agents → https://code.visualstudio.com/docs/copilot/chat/
+   - General Copilot → https://code.visualstudio.com/docs/copilot/ or
+   https://docs.github.com/en/copilot/
+
+2. **Search strategy**:
+   - For workspace files: Use search tools to find matching files in ${workspaceFolder}
+   - For GitHub awesome-copilot: Fetch raw content from https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/
+   - For documentation: Use fetch tool with the most relevant URL from above
+
+3. **Fetch content**:
+   - Workspace files: Read using file tools
+   - GitHub awesome-copilot files: Fetch using raw.githubusercontent.com URLs
+   - Documentation URLs: Fetch using fetch tool
+
+4. **Evaluate and respond**:
+   - Use the fetched content as the reference for completing the request
+   - Adapt response verbosity based on chat context
+
+### Unambiguous Queries
+
+If the user **DOES** provide a specific URL or file, skip searching and fetch/read that directly.
+
+### Optional
+
+* **Help output** - Raw data matching `-h`, `--help`, `/?`, `--tldr`, `--man`, etc.
+
+## Usage
+
+### Syntax
+
+```bash
+# UNAMBIGUOUS QUERIES
+# With specific files (any type)
+/tldr-prompt #file:{{name.prompt.md}}
+/tldr-prompt #file:{{name.agent.md}}
+/tldr-prompt #file:{{name.instructions.md}}
+/tldr-prompt #file:{{name.collections.md}}
+
+# With URLs
+/tldr-prompt #fetch {{https://example.com/docs}}
+
+# AMBIGUOUS QUERIES
+/tldr-prompt "{{topic or question}}"
+/tldr-prompt "MCP servers"
+/tldr-prompt "inline chat shortcuts"
+```
+
+### Error Handling
+
+#### Missing Required Parameters
+
+**User**
+
+```bash
+/tldr-prompt
+```
+
+**Agent Response when NO Required Data**
+
+```text
+Error: Missing required input.
+
+You MUST provide one of the following:
+1. A Copilot file: /tldr-prompt #file:{{name.prompt.md | name.agent.md | name.instructions.md | name.collections.md}}
+2. A URL: /tldr-prompt #fetch {{https://example.com/docs}}
+3. A search query: /tldr-prompt "{{topic}}" (e.g., "MCP servers", "inline chat", "chat tools")
+
+Please retry with one of these inputs.
+```
+
+### AMBIGUOUS QUERIES
+
+#### Workspace Search
+
+> [!NOTE]
+> First attempt to resolve using workspace files. If found, generate output. If no relevant files found,
+> resolve using GitHub awesome-copilot as specified in **URL Resolver** section.
+
+**User**
+
+```bash
+/tldr-prompt "Prompt files relevant to Java"
+```
+
+**Agent Response when Relevant Workspace Files Found**
+
+```text
+I'll search ${workspaceFolder} for Copilot customization files (.prompt.md, .agent.md, .instructions.md, .collections.md) relevant to Java.
+From the search results, I'll produce a tldr output for each file found.
+```
+
+**Agent Response when NO Relevant Workspace Files Found**
+
+```text
+I'll check https://github.com/github/awesome-copilot
+Found:
+- https://github.com/github/awesome-copilot/blob/main/prompts/java-docs.prompt.md
+- https://github.com/github/awesome-copilot/blob/main/prompts/java-junit.prompt.md
+
+Now let me fetch the raw content:
+- https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-docs.prompt.md
+- https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-junit.prompt.md
+
+I'll create a tldr summary for each prompt file.
+```
+
+### UNAMBIGUOUS QUERIES
+
+#### File Query
+
+**User**
+
+```bash
+/tldr-prompt #file:typescript-mcp-server-generator.prompt.md
+```
+
+**Agent**
+
+```text
+I'll read the file typescript-mcp-server-generator.prompt.md and create a tldr summary.
+```
+
+#### Documentation Query
+
+**User**
+
+```bash
+/tldr-prompt "How do MCP servers work?" #fetch https://code.visualstudio.com/docs/copilot/customization/mcp-servers
+```
+
+**Agent**
+
+```text
+I'll fetch the MCP server documentation from https://code.visualstudio.com/docs/copilot/customization/mcp-servers
+and create a tldr summary of how MCP servers work.
+```
+
+## Workflow
+
+You MUST follow these steps in order:
+
+1. **Validate Input**: Confirm at least one required parameter is provided. If not, output the error
+message from Error Handling section
+2. **Identify Context**:
+   - Determine file type (.prompt.md, .agent.md, .instructions.md, .collections.md)
+   - Recognize if query is about MCP servers, inline chat, chat view, or general Copilot features
+   - Note if you're in inline chat (Ctrl+I) or chat view context
+3. **Fetch Content**:
+   - For files: Read the file(s) using available file tools
+   - For URLs: Fetch content using `#tool:fetch`
+   - For queries: Apply URL Resolver strategy to find and fetch relevant content
+4. **Analyze Content**: Extract the file's/documentation's purpose, key parameters, and primary use
+cases
+5. **Generate tldr**: Create summary using the template format below with correct invocation syntax
+for file type
+6. **Format Output**:
+   - Ensure markdown formatting is correct with proper code blocks and placeholders
+   - Use appropriate invocation prefix: `/` for prompts, `@` for agents, context-specific for
+   instructions/collections
+   - Adapt verbosity: inline chat = concise, chat view = detailed
+
+## Template
+
+Use this template structure when creating tldr pages:
+
+```markdown
+# command
+
+> Short, snappy description.
+> One to two sentences summarizing the prompt or prompt documentation.
+> More information: <name.prompt.md> | <URL/prompt>.
+
+- View documentation for creating something:
+
+`/file command-subcommand1`
+
+- View documentation for managing something:
+
+`/file command-subcommand2`
+```
+
+### Template Guidelines
+
+You MUST follow these formatting rules:
+
+- **Title**: You MUST use the exact filename without extension (e.g., `typescript-mcp-expert` for
+.agent.md, `tldr-page` for .prompt.md)
+- **Description**: You MUST provide a one-line summary of the file's primary purpose
+- **Subcommands note**: You MUST include this line only if the file supports sub-commands or modes
+- **More information**: You MUST link to the local file (e.g., `<name.prompt.md>`, `<name.agent.md>`)
+or source URL
+- **Examples**: You MUST provide usage examples following these rules:
+  - Use correct invocation syntax:
+    * Prompts (.prompt.md): `/prompt-name {{parameters}}`
+    * Agents (.agent.md): `@agent-name {{request}}`
+    * Instructions (.instructions.md): Context-based (document how they apply)
+    * Collections (.collections.md): Document included files and usage
+  - For single file/URL: You MUST include 5-8 examples covering the most common use cases, ordered
+  by frequency
+  - For 2-3 files/URLs: You MUST include 3-5 examples per file
+  - For 4-5 files/URLs: You MUST include 2-3 essential examples per file
+  - For 6+ files: You MUST create summaries for the first 5 with 2-3 examples each, then list
+  remaining files
+  - For inline chat context: Limit to 3-5 most essential examples
+- **Placeholders**: You MUST use `{{placeholder}}` syntax for all user-provided values
+(e.g., `{{filename}}`, `{{url}}`, `{{parameter}}`)
+
+## Success Criteria
+
+Your output is complete when:
+
+- ✓ All required sections are present (title, description, more information, examples)
+- ✓ Markdown formatting is valid with proper code blocks
+- ✓ Examples use correct invocation syntax for file type (/ for prompts, @ for agents)
+- ✓ Examples use `{{placeholder}}` syntax consistently for user-provided values
+- ✓ Output is rendered directly in chat, not as a file creation
+- ✓ Content accurately reflects the source file's/documentation's purpose and usage
+- ✓ Response verbosity is appropriate for chat context (inline chat vs chat view)
+- ✓ MCP server content includes setup and tool usage examples when applicable

package/skills/tldr-prompt/SYNC.md

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

package/skills/transloadit-media-processing/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/transloadit-media-processing/SKILL.md

@@ -0,0 +1,194 @@
+---
+name: transloadit-media-processing
+description: 'Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS/MP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.'
+license: MIT
+compatibility: Requires a free Transloadit account (https://transloadit.com/signup). Uses the @transloadit/mcp-server MCP server or the @transloadit/node CLI.
+---
+
+# Transloadit Media Processing
+
+Process, transform, and encode media files using Transloadit's cloud infrastructure.
+Supports video, audio, images, and documents with 86+ specialized processing robots.
+
+## When to Use This Skill
+
+Use this skill when you need to:
+
+- Encode video to HLS, MP4, WebM, or other formats
+- Generate thumbnails or animated GIFs from video
+- Resize, crop, watermark, or optimize images
+- Convert between image formats (JPEG, PNG, WebP, AVIF, HEIF)
+- Extract or transcode audio (MP3, AAC, FLAC, WAV)
+- Concatenate video or audio clips
+- Add subtitles or overlay text on video
+- OCR documents (PDF, scanned images)
+- Run speech-to-text or text-to-speech
+- Apply AI-based content moderation or object detection
+- Build multi-step media pipelines that chain operations together
+
+## Setup
+
+### Option A: MCP Server (recommended for Copilot)
+
+Add the Transloadit MCP server to your IDE config. This gives the agent direct access
+to Transloadit tools (`create_template`, `create_assembly`, `list_assembly_notifications`, etc.).
+
+**VS Code / GitHub Copilot** (`.vscode/mcp.json` or user settings):
+
+```json
+{
+  "servers": {
+    "transloadit": {
+      "command": "npx",
+      "args": ["-y", "@transloadit/mcp-server", "stdio"],
+      "env": {
+        "TRANSLOADIT_KEY": "YOUR_AUTH_KEY",
+        "TRANSLOADIT_SECRET": "YOUR_AUTH_SECRET"
+      }
+    }
+  }
+}
+```
+
+Get your API credentials at https://transloadit.com/c/-/api-credentials
+
+### Option B: CLI
+
+If you prefer running commands directly:
+
+```bash
+npx -y @transloadit/node assemblies create \
+  --steps '{"encoded": {"robot": "/video/encode", "use": ":original", "preset": "hls-1080p"}}' \
+  --wait \
+  --input ./my-video.mp4
+```
+
+## Core Workflows
+
+### Encode Video to HLS (Adaptive Streaming)
+
+```json
+{
+  "steps": {
+    "encoded": {
+      "robot": "/video/encode",
+      "use": ":original",
+      "preset": "hls-1080p"
+    }
+  }
+}
+```
+
+### Generate Thumbnails from Video
+
+```json
+{
+  "steps": {
+    "thumbnails": {
+      "robot": "/video/thumbs",
+      "use": ":original",
+      "count": 8,
+      "width": 320,
+      "height": 240
+    }
+  }
+}
+```
+
+### Resize and Watermark Images
+
+```json
+{
+  "steps": {
+    "resized": {
+      "robot": "/image/resize",
+      "use": ":original",
+      "width": 1200,
+      "height": 800,
+      "resize_strategy": "fit"
+    },
+    "watermarked": {
+      "robot": "/image/resize",
+      "use": "resized",
+      "watermark_url": "https://example.com/logo.png",
+      "watermark_position": "bottom-right",
+      "watermark_size": "15%"
+    }
+  }
+}
+```
+
+### OCR a Document
+
+```json
+{
+  "steps": {
+    "recognized": {
+      "robot": "/document/ocr",
+      "use": ":original",
+      "provider": "aws",
+      "format": "text"
+    }
+  }
+}
+```
+
+### Concatenate Audio Clips
+
+```json
+{
+  "steps": {
+    "imported": {
+      "robot": "/http/import",
+      "url": ["https://example.com/clip1.mp3", "https://example.com/clip2.mp3"]
+    },
+    "concatenated": {
+      "robot": "/audio/concat",
+      "use": "imported",
+      "preset": "mp3"
+    }
+  }
+}
+```
+
+## Multi-Step Pipelines
+
+Steps can be chained using the `"use"` field. Each step references a previous step's output:
+
+```json
+{
+  "steps": {
+    "resized": {
+      "robot": "/image/resize",
+      "use": ":original",
+      "width": 1920
+    },
+    "optimized": {
+      "robot": "/image/optimize",
+      "use": "resized"
+    },
+    "exported": {
+      "robot": "/s3/store",
+      "use": "optimized",
+      "bucket": "my-bucket",
+      "path": "processed/${file.name}"
+    }
+  }
+}
+```
+
+## Key Concepts
+
+- **Assembly**: A single processing job. Created via `create_assembly` (MCP) or `assemblies create` (CLI).
+- **Template**: A reusable set of steps stored on Transloadit. Created via `create_template` (MCP) or `templates create` (CLI).
+- **Robot**: A processing unit (e.g., `/video/encode`, `/image/resize`). See full list at https://transloadit.com/docs/transcoding/
+- **Steps**: JSON object defining the pipeline. Each key is a step name, each value configures a robot.
+- **`:original`**: Refers to the uploaded input file.
+
+## Tips
+
+- Use `--wait` with the CLI to block until processing completes.
+- Use `preset` values (e.g., `"hls-1080p"`, `"mp3"`, `"webp"`) for common format targets instead of specifying every parameter.
+- Chain `"use": "step_name"` to build multi-step pipelines without intermediate downloads.
+- For batch processing, use `/http/import` to pull files from URLs, S3, GCS, Azure, FTP, or Dropbox.
+- Templates can include `${variables}` for dynamic values passed at assembly creation time.

package/skills/transloadit-media-processing/SYNC.md

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

package/skills/typescript-mcp-server-generator/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/typescript-mcp-server-generator/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: typescript-mcp-server-generator
+description: 'Generate a complete MCP server project in TypeScript with tools, resources, and proper configuration'
+---
+
+# Generate TypeScript MCP Server
+
+Create a complete Model Context Protocol (MCP) server in TypeScript with the following specifications:
+
+## Requirements
+
+1. **Project Structure**: Create a new TypeScript/Node.js project with proper directory structure
+2. **NPM Packages**: Include @modelcontextprotocol/sdk, zod@3, and either express (for HTTP) or stdio support
+3. **TypeScript Configuration**: Proper tsconfig.json with ES modules support
+4. **Server Type**: Choose between HTTP (with Streamable HTTP transport) or stdio-based server
+5. **Tools**: Create at least one useful tool with proper schema validation
+6. **Error Handling**: Include comprehensive error handling and validation
+
+## Implementation Details
+
+### Project Setup
+- Initialize with `npm init` and create package.json
+- Install dependencies: `@modelcontextprotocol/sdk`, `zod@3`, and transport-specific packages
+- Configure TypeScript with ES modules: `"type": "module"` in package.json
+- Add dev dependencies: `tsx` or `ts-node` for development
+- Create proper .gitignore file
+
+### Server Configuration
+- Use `McpServer` class for high-level implementation
+- Set server name and version
+- Choose appropriate transport (StreamableHTTPServerTransport or StdioServerTransport)
+- For HTTP: set up Express with proper middleware and error handling
+- For stdio: use StdioServerTransport directly
+
+### Tool Implementation
+- Use `registerTool()` method with descriptive names
+- Define schemas using zod for input and output validation
+- Provide clear `title` and `description` fields
+- Return both `content` and `structuredContent` in results
+- Implement proper error handling with try-catch blocks
+- Support async operations where appropriate
+
+### Resource/Prompt Setup (Optional)
+- Add resources using `registerResource()` with ResourceTemplate for dynamic URIs
+- Add prompts using `registerPrompt()` with argument schemas
+- Consider adding completion support for better UX
+
+### Code Quality
+- Use TypeScript for type safety
+- Follow async/await patterns consistently
+- Implement proper cleanup on transport close events
+- Use environment variables for configuration
+- Add inline comments for complex logic
+- Structure code with clear separation of concerns
+
+## Example Tool Types to Consider
+- Data processing and transformation
+- External API integrations
+- File system operations (read, search, analyze)
+- Database queries
+- Text analysis or summarization (with sampling)
+- System information retrieval
+
+## Configuration Options
+- **For HTTP Servers**: 
+  - Port configuration via environment variables
+  - CORS setup for browser clients
+  - Session management (stateless vs stateful)
+  - DNS rebinding protection for local servers
+  
+- **For stdio Servers**:
+  - Proper stdin/stdout handling
+  - Environment-based configuration
+  - Process lifecycle management
+
+## Testing Guidance
+- Explain how to run the server (`npm start` or `npx tsx server.ts`)
+- Provide MCP Inspector command: `npx @modelcontextprotocol/inspector`
+- For HTTP servers, include connection URL: `http://localhost:PORT/mcp`
+- Include example tool invocations
+- Add troubleshooting tips for common issues
+
+## Additional Features to Consider
+- Sampling support for LLM-powered tools
+- User input elicitation for interactive workflows
+- Dynamic tool registration with enable/disable capabilities
+- Notification debouncing for bulk updates
+- Resource links for efficient data references
+
+Generate a complete, production-ready MCP server with comprehensive documentation, type safety, and error handling.

package/skills/typescript-mcp-server-generator/SYNC.md

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