ProfessorGPTProfessorGPT
Official Provider SkillView repo

Write a short three-line project status report in Markdown. Use when asked for a status report.

Files1 files
SKILL.md20 lines
Loading editor…

Install

Recommended

One command — your agent picks it up automatically.

Select an AI agent above to see the install command.

or

Manual Install

More steps

Download the file and paste it into your agent's system prompt.

Skill details

Versionv1.0.0
AuthorMicrosoft
Categoryanalysis
Skill IDmicrosoft/amplifier-agent/evaluations/tasks/tools/skill/workspace/.agents/skills/status-report

Related skills

Amplifier AgentIntegrate Amplifier Agent into applications using its Python or TypeScript library or OpenAI-compatible HTTP face. Use for installation, sessions, streaming, tools, MCP, skills, approvals, configuration, and integration troubleshooting.Amplifier Agent BugfixTriage and fix an amplifier-agent bug, from report to verified fix. Covers intake, ruling out non-code causes, root-cause pinning, checking the behavior against the contracts, the coverage-gap gate, red/green regression with evaluations and tests, scoped verification, and quality regressions where contracts hold but output got worse. Stops before commit and release.Amplifier Agent New FeatureDevelop a new amplifier-agent feature from idea to verified behavior. Covers orientation against the contracts, planning, updating every public description, red/green development driven by an evaluation task and supporting tests, the widening verification ladder, and a hands-on human check. Stops before commit and release.Echo ArgsWrites the exact text it received as arguments, verbatim, to a file. Used to verify skill argument passthrough.Tool ProbeWrites a fixed sentinel to a file to prove the agent invoked this skill through its skills tool in response to a natural-language request. Invoke this skill when asked to run or invoke tool-probe.Auto Perf OptimizeRun agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.