mcs-lab-issue-filer Skill
Convert a lab's findings.json into a GitHub issue body and file it against the active instance's lab repo (microsoft/mcs-labs by default). Checks for an existing open issue with matching labels and comments on it instead of duplicating. Invoked by mcs-lab-auditor after a lab completes with at least one judge-recorded f Published by microsoft in BootcampLabTestPlugin.
What is mcs-lab-issue-filer Skill?
Convert a lab's findings.json into a GitHub issue body and file it against the active instance's lab repo (microsoft/mcs-labs by default). Checks for an existing open issue with matching labels and comments on it instead of duplicating. Invoked by mcs-lab-auditor after a lab completes with at least one judge-recorded f Published by microsoft in BootcampLabTestPlugin. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Technical details
- Install or run with Copy skill directory
When to use mcs-lab-issue-filer Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/BootcampLabTestPlugin
- Skill file: skills/mcs-lab-issue-filer/SKILL.md
What it does
Convert a lab's findings.json into a GitHub issue body and file it against the active instance's lab repo (microsoft/mcs-labs by default). Checks for an existing open issue with matching labels and comments on it instead of duplicating. Invoked by mcs-lab-auditor after a lab completes with at least one judge-recorded f
Skill instructions
mcs-lab-issue-filer (sub-skill) Take the findings for one lab from one audit run and either (a) file a new GitHub issue or (b) comment on an existing open issue for the same lab. Then record the result in manifest.yml and audit-history.yml. Inputs (assumed present) - runs/<run-id/labs/<slug/findings.json — list of finding records (see ../mcs-lab-auditor/references/finding-schema.md). - runs/<run-id/manifest.yml — for the run-id, account user-id, plugin-version, etc. - <plugin/config/judge-config.yml — for confidence thresholds, label config, dedupe behavior. - C:\Users\dewainr\mcs-labs\labs<slug.md — for the lab title (front-matter). Outputs - runs/<run-id/labs/<slug/issue-body.md — the rendered issue body (kept on disk for audit + retry). - New or updated issue at github.com/{repo}/issues/<n. - Updated manifest.yml.labs[<slug]: status: issuefiled, issueurl, issueaction: created|commented. - Updated runtime/audit-history.yml: appended entry per audit-log-schema.md. Procedure 1. Load i
Explore related resources
Frequently asked questions
What is mcs-lab-issue-filer?
mcs-lab-issue-filer is a open-source AI agent skill with Copy skill directory. Convert a lab's findings.json into a GitHub issue body and file it against the active instance's lab repo (microsoft/mcs-labs by default).
Who is mcs-lab-issue-filer best for?
mcs-lab-issue-filer is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install mcs-lab-issue-filer?
Install or run mcs-lab-issue-filer using Copy skill directory. Check mcs-lab-issue-filer for the latest setup command.
Is mcs-lab-issue-filer actively maintained?
mcs-lab-issue-filer may need a closer maintenance check before production use.
Auto-fetched from GitHub.
