microsoft/team-request
plugins/github-copilot-modernization/skills/team-request/SKILL.md
How team members request infrastructure connection info and handle secrets in team mode
$ install --global
skillsauthnpx skillsauth add microsoft/github-copilot-modernization team-requestInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 28, 2026, 5:12 AM51.0s1 file scanned
SKILL.md
- name:
- team-request
- description:
- How team members request infrastructure connection info and handle secrets in team mode
Team requests
This skill is automatically loaded for all team members in team mode. It defines the requests that team members can make to each other.
Requesting Infrastructure Connection Info
When your task requires connection to real Azure resources (databases, queues, storage, etc.), use the request tool to ask the InfrastructureExpert for connection values.
What the InfrastructureExpert provides:
- Connection strings (e.g., for databases, message queues, storage)
- Endpoint URLs with managed identity configuration
- Confirmation of resource changes you requested
Workflow:
- Before performing work that requires real resource connections, call:
request(from: "<your-name>", to: "<InfrastructureExpert-name>", taskId: "<your-task-id>", message: "I need the connection string for the PostgreSQL database") - The response contains ONLY the connection values — no subscription/RG/resource IDs.
- Use the returned values to configure your code or tests.
Requesting resource changes:
If you need a resource modification (e.g., create a test database, add a firewall rule, create a queue, assign a role), use the request tool with a message describing the change. Do NOT attempt to run az commands yourself for resource provisioning.
Example:
request(from: "ITTester", to: "InfraExpert", taskId: "003-integrationTest", message: "Create a test database named 'app_test' on the PostgreSQL server and return the connection string with managed identity auth")
Related Skills
microsoft/verify-test-baseline
testing
VerifiedTrustedCommunity
Generate and run post-migration tests from the frozen baseline specification.
40SKILL.mdUpdated Aug 28, 2026
microsoft/create-test-baseline
testing
VerifiedTrustedCommunity
Create a test baseline for the project to be modernized. The baseline will be used for later verification of modernization tasks.
40SKILL.mdUpdated Aug 28, 2026
microsoft/assessment-report-converter
tools
VerifiedTrustedCommunity
Convert an arbitrary CSV report (e.g. a Black Duck export or a custom migration-issue inventory) into a schema-valid assessment `report.json` the modernization pipeline can consume — so it appears in the assessment UI and migration solutions resolve automatically. This skill is LLM-driven: you read and interpret the CSV yourself and author `report.json` by hand against the schema. A small helper script only does deterministic lookups (migration solutions, the ruleId for a solution) and validates the finished report. There is NO "convert everything" script and NO assumed column layout. Triggers: "convert csv to assessment report", "import csv report", "turn this spreadsheet into a report.json", "Black Duck csv to report", "build report.json from csv", "migrate a third-party assessment export". NOT for: AppCAT-style analysis from source (use `assessment`), generating a modernization plan (use `create-modernization-plan`), or editing a report.json the pipeline already produced.
40SKILL.mdUpdated Aug 28, 2026
microsoft/modernization-integration-tests
development
VerifiedTrustedCommunity
Run multi-layer integration tests for modernized Java applications. Supports 4 layers - Layer 1 (TestContainers), Layer 2 (Smoke Tests), Layer 3 (Azure Integration), Layer 4 (Behavioral Comparison). Java projects only - skip if source code is not Java. Triggers: "generate integration tests", "add integration tests", "create Layer 1 tests", "create Layer 2 tests" NOT for: unit tests, performance tests, load tests.
40SKILL.mdUpdated May 14, 2026