GitHub

Prepare raw credit data for pre-loan modeling by checking data quality and screening variables. Review missing values, predictive usefulness, stability, noise, and correlation, then export an Excel report with organization-level statistics and cleaning results.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare credit data before building a model
• Compare missing values and bad-sample rates across organizations
• Screen variables for usefulness, stability, and redundancy

Create, design, and validate agents for Microsoft 365 Copilot. The skill guides JSON configuration or TypeSpec definitions, a typed alternative, alongside local testing, enterprise requirements, and deployment planning with Microsoft 365 Agents Toolkit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a prototype agent for Microsoft 365 Copilot
• Plan enterprise features and multilingual support
• Validate an existing agent's configuration

Creates software documentation using Diátaxis, a framework that separates learning, task instructions, reference information, and explanation. Clarifies the audience, goal, and scope, then proposes an outline before writing Markdown content consistent with existing documentation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing a practical tutorial for newcomers
• Creating a guide to solve a specific problem
• Organizing technical details into reference documentation

Write consistent XML documentation comments for C# types and public members. Follow specific rules for summaries, parameters, return values, properties, exceptions, examples, and inherited documentation so API behavior and usage are clearly described alongside the code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding documentation to public APIs
• Standardizing parameter and return value descriptions
• Documenting exception conditions and usage examples

Turn defects found during Oracle-to-PostgreSQL migration into structured bug reports. Document expected and actual behavior, reproduction steps, severity, root causes, proposed changes, and validation on both databases so teams can act on the findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting behavioral differences found during migration
• Organizing reproduction steps and test data
• Recording fixes, affected files, and validation steps

Build and troubleshoot C#/.NET MCP servers that expose tools and information to AI agents. Guidance targets the official 2.x SDK and covers transport setup, authentication, interactive features, basic clients, and migration issues caused by changed defaults.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a C#/.NET MCP server
• Add tools, prompts, and resources
• Diagnose STDIO and HTTP connection errors

Write focused C# unit tests with XUnit, including tests that run against multiple input datasets. Apply consistent naming, setup, assertions, shared fixtures, and mock dependencies to keep tests readable, independent, and organized.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up an XUnit test project for C#
• Test multiple input cases with Theory and data attributes
• Check exceptions and isolate dependencies with mocks

Turn official command documentation into a concise tldr page, an example-based command reference. Provide a command name and documentation URL to get five to eight common usage examples with consistent formatting and placeholders.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a quick reference from a lengthy command manual
• Organize common command usage into five to eight examples
• Format command examples according to tldr conventions

Turn a business use case into a Dataverse solution using Python. Get table and relationship designs, implementation code, usage instructions, and recommendations for error recovery, logging, monitoring, and performance based on the expected workload.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing customer and document management solutions
• Building data migration or scheduled synchronization jobs
• Implementing order processing and approval workflows

Create rollout plans for application and infrastructure changes. Organize readiness checks, deployment steps, health indicators, rollback procedures, and stakeholder communications, adapting the detail to the target environment, change type, and level of risk.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a production deployment plan
• Define rollback steps and decision criteria
• Set post-deployment health checks

Turn a specification file into a GitHub feature request issue. The skill extracts requirements, checks existing issues, and creates or updates one issue covering the specification, using a template to organize the problem, solution, and context.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn a specification into a feature request issue
• Check existing issues before registering a request
• Update an existing issue with specification requirements

Configure GitHub Dependabot to keep dependencies, the packages a project relies on, updated. Organize update pull requests into groups, set schedules and exclusion rules, and configure security updates across projects with multiple packages or package systems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create or revise dependabot.yml
• Group dependency updates into fewer pull requests
• Configure updates across a monorepo

Create integration tests for .NET database access before migrating from Oracle to PostgreSQL. The tests record expected Oracle behavior with controlled test data and portable checks, providing a baseline for later migration validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording Oracle behavior before migration
• Testing repository methods and stored procedure calls
• Checking empty strings, NULL inputs, and datetime precision

Generate an .editorconfig file tailored to a project's file types and formatting preferences. Set indentation, line endings, character encoding, and whitespace rules, with a clear explanation of each choice to support consistent formatting across editors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Standardize formatting across team members' editors
• Set indentation rules for different file types
• Define line ending and whitespace settings

Create Markdown documents for time-limited technical investigations before implementation. Define the decision to resolve, research tasks, success criteria, and deadlines, then record evidence, recommendations, and follow-up actions in a consistent structure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating API capabilities before integration
• Comparing architecture options before implementation
• Planning experiments to check performance assumptions

Create and edit draw.io files for workflows, system architecture, database relationships, and service interactions. Organize shapes and connectors, apply consistent styling, and check file structure so diagrams can be opened and edited in draw.io.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn business processes into flowcharts
• Document system components and connections
• Diagram database tables and relationships

Create a Spring Boot Java project skeleton with Maven, database connection settings, and Docker Compose services. Adds dependencies for API documentation and architecture tests, then checks the generated project with a Maven test command.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Start a Java 21 Spring Boot project
• Prepare local PostgreSQL, Redis, and MongoDB services
• Add API documentation and architecture test dependencies

Document a local codebase with file references, architecture diagrams, and verified project commands. For legacy modernization, assess what still runs and create a phased migration plan with validation methods suited to each component’s current condition.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an onboarding guide for a codebase
• Mapping system architecture and dependencies
• Planning a legacy system migration or rewrite

Create structured Markdown specifications that AI agents can read and use. Organize requirements, constraints, interfaces, acceptance criteria, and testing plans into a self-contained document with clear definitions and examples.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing specifications for AI-assisted implementation
• Defining requirements and acceptance criteria
• Documenting APIs and data contracts

Build a Solution Blueprint for a Dynamics 365 Finance and Supply Chain Management implementation through guided interviews. Define scope and architecture, compare options, and document decisions, their rationale, assumptions, and unresolved questions across working sessions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create an architecture blueprint for a new D365 implementation
• Define implementation scope and rollout phases
• Compare data migration and integration approaches

Provides prompts for assessing and planning .NET upgrades across multiple projects. Helps identify compatibility issues, order migration work, propose code and build pipeline changes, and prepare testing checklists, review guidance, and release documentation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assessing project structure and dependency compatibility
• Planning an incremental upgrade with rollback checkpoints
• Reviewing deprecated APIs and NuGet package replacements

Create an Architectural Decision Record, a document explaining a system design choice. Organize context, rationale, alternatives, benefits, drawbacks, and implementation notes in consistent Markdown that people can read and AI tools can parse.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording the reasons behind a system design choice
• Documenting rejected alternatives and trade-offs
• Sharing decision context with new team members

Convert Word documents into Markdown text for summarizing, searching, comparing, or extracting information. The bundled script saves embedded images alongside each document and supports processing entire folders, including subfolders, before the agent analyzes the converted content.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare Word reports for summarization
• Extract information from resumes or proposals
• Convert a folder of Word documents in one batch

Document bug fixes and incident recovery with a structured receipt covering the problem, cause, change, and verification evidence. Distinguishes verified results from partial or blocked work, identifies missing proof, and specifies the next check needed to close the gap.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Record the evidence supporting a bug fix
• Report missing checks after a partial repair
• Document an incident blocked by an external condition