AGENT SKILL

team-request

How team members request infrastructure connection info and handle secrets in team mode

License 许可
MIT
最近更新
2026-09-24
Stars
★ 55
Forks
15

01 前言 Front Matter

name
team-request
description
How team members request infrastructure connection info and handle secrets in team mode

03 SKILL.md 正文

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:

  1. 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")
    
  2. The response contains ONLY the connection values — no subscription/RG/resource IDs.
  3. 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")

04 同仓库更多 Skills

microsoft
microsoft/github-copilot-modernization

verify-test-baseline

Generate and run post-migration tests from the frozen baseline specification.

测试与质量
★ 55
microsoft
microsoft/github-copilot-modernization

team-charters

Provides role charters (mission, ownership, core principles, quality bar) for a multi-agent coding team. Each charter defines the role's mission, ownership scope, core principle (boundary constraints), and quality bar. Most roles also include communication rules. Consumed by the coordinator during task decomposition to assign work to the correct role. Triggers: "look up role charter", "what does the architect own", "check role boundaries", "find team roles", "which role handles X", "list agent charters", "role responsibilities". NOT for: task decomposition (use breaking-down-tasks), implementation (use implementing-code), architecture analysis (use analyzing-architecture).

★ 55
microsoft
microsoft/github-copilot-modernization

struts-to-spring

Migration guideline for transforming Apache Struts 2 applications to Spring Boot 3.x and Spring MVC.

★ 55
microsoft
microsoft/github-copilot-modernization

spring-boot-scaffolding

Reference guide for creating a new Spring Boot project during rewrite migration.

★ 55
microsoft
microsoft/github-copilot-modernization

sharing-learnings

How to record project learnings so that later-phase workers and future agent runs can consume them.

★ 55
microsoft
microsoft/github-copilot-modernization

setting-up-constitution

Creates or updates the project constitution that defines migration principles, constraints, and conventions. Triggers: "set up constitution", "define migration principles", "create project rules", "establish conventions", "establish migration constitution". NOT for: implementation, implementation planning, task generation.

★ 55