Agent Mode Instructions

This page separates teammate-facing guidance from copyable agent-operational instructions for the SDMCC Agent Skills library.

Human Mode

Use Human Mode when a teammate is deciding whether a skill is appropriate, reviewed, and safe to install.

Check these items before installing or promoting a skill:

• The skill appears in the root README.md skill index with the same status shown in skills/<skill-name>/README.md.
• The status is one of Experimental, Team Review, Production Ready, Required, or Deprecated.
• SKILL.md has valid frontmatter and describes a repeatable workflow.
• The skill README names purpose, requirements, example prompts, and expected output.
• Project-specific identity and Azure DevOps behavior live in skills/azure-devops-pbi/references/project-profile.md or another clearly named reference file.
• Validation evidence is current for the files being changed.

Use this copyable teammate checklist:

Review the SDMCC Agent Skills repository before installing or promoting a skill. Confirm README.md and the skill README show the same status, read CONTRIBUTING.md and AGENTS.md, inspect the skill README and SKILL.md, check project-specific references under skills/<skill-name>/references/ when present, and ask for validation evidence before broad use. Do not install globally just because a skill is committed here.

Agent Mode

Use Agent Mode when you want an agent to inspect, install, validate, or report on SDMCC skills.

Copy this prompt into the agent session:

Use the SDMCC Agent Skills repository at https://dev.azure.com/difzses/SDMCC/_git/SDMCC-Agent-Skills. Read README.md, AGENTS.md, CONTRIBUTING.md, docs/installing-agent-skills.md, docs/new-user-setup.md, docs/agent-mode-instructions.md, docs/skill-field-reports.md, and skills/azure-devops-pbi/references/project-profile.md when the Azure DevOps PBI skill is involved. Install only the requested skill for the requested host. If you are Codex, use scripts/setup-azure-devops-pbi-skill.sh codex for azure-devops-pbi or scripts/install-skill.sh <skill-name> codex for other skills. If I ask for GitHub Copilot or Cursor, use the matching documented command and project path. Use normal az login with my work account when Azure DevOps access is required. Do not ask for a shared PAT, dashboard API key, AWS secret, Cognito credential, raw token, .env file, .mcp.json, or deployment log. Validate with the repo commands that match your change and summarize changed files, validation, blockers, and any safe field report categories that apply.

For install-only work, use the shortest supported command:

scripts/setup-azure-devops-pbi-skill.sh codex

scripts/setup-azure-devops-pbi-skill.sh copilot /path/to/project-repo

scripts/setup-azure-devops-pbi-skill.sh cursor /path/to/project-repo

For non-PBI skills, use the generic helper:

scripts/install-skill.sh <skill-name> codex

scripts/install-skill.sh <skill-name> copilot /path/to/project-repo

scripts/install-skill.sh <skill-name> cursor /path/to/project-repo

Agent Reporting

When a skill run finishes, the agent should report:

• Skill inspected or installed.
• Host target used.
• Files changed, if any.
• Validation commands run and whether they passed.
• Blockers or unavailable checks.
• Safe field-report category from docs/skill-field-reports.md when the experience produced reusable operational signal.

Do not include raw prompts, transcripts, local paths outside the repo, credentials, PATs, tokens, secret names with values, deployment logs, or full Azure Boards comments in agent reports.