194건 · 관련도순
Turn validated Codex Security findings into tracked work in Linear, Jira, GitHub issues, or draft GitHub security advisories. Check for duplicates, preview exact content and audience, and record approved creations, updates, or reuse.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn rough feature ideas into a clear SPEC.md through focused questions. Define target users, business rules, current scope, and acceptance criteria based on observable results, giving developers or AI agents concrete requirements to implement.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and edit Google Docs while preserving requested structure, formatting, tabs, and tables. Adapt templates using current source information, update links and smart chips, and check that the finished document covers the requested content.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn validated Codex Security findings into tracked issues in Linear, Jira, or GitHub, or draft GitHub security advisories. Checks duplicates and visibility, previews exact changes for approval, and verifies results after writing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Examines code or code changes for plausible security vulnerabilities by tracing attacker-controlled input to dangerous operations or failed safeguards. Records candidate issues with affected locations, supporting evidence, potential impact, and controls that need further validation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate MSBuild failures, measure slow builds, or review existing build definitions. Use binary logs, project settings, and comparable timing measurements to identify causes, propose focused repairs, and verify behavior without broad configuration changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Set up personal AI agents that join Squad sessions across projects. Manage their roles in a user configuration directory, inspect the combined team, and use agents that read project state and offer advice without writing to it.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review research ethics, participant protection, and potential bias from planning through publication. The skill examines questionable research practices and study trustworthiness, then produces a structured report with evidence, risk levels, and prioritized recommendations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Queue open microsoft/apm issues and fan them out through an isolated pool (default 2) of autopilot-issue-triage-worker sessions. Advisory only. Never implements, never assigns, never requests reviewers. Activate on a mixed issue list or queue-all when the job is triage. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to triage ONE microsoft/apm pull request already selected by autopilot-pr-triage-scheduler. Covers community PRs that fix an issue and PRs opened without an issue. Return one advisory recommendation, never human approval, never a diff review, never merge. Not a queue manager and not autopilot-pr-review-worker.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code. Activate when you have specific pages to check for factual accuracy -- not when sweeping a whole corpus (use docs-corpus-audit for that) and not when triaging a PR diff (use docs-sync for that). Trigger nouns: "is this doc accurate", "verify the page against the code", "fact-check this section", "any claims that drifted from source", "fact-checking", "grounding audit", "drift hunt", "claim verification". Returns per-claim verdicts (GROUNDED | PARTIAL | CONTRADICTED | UNSUPPORTED) with file:line evidence citations. Catches paragraph-level inaccuracies that page-level audit averages over -- e.g. a paragraph with 5 claims where 4 are grounded and 1 is fabricated. Does NOT modify files (returns advisory only); does NOT re-architect the docs; does NOT triage PRs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to triage ONE microsoft/apm issue already selected by autopilot-issue-triage-scheduler. Return one advisory recommendation and a proposed scope brief, never human approval. Do not implement the issue, manage the backlog, or list the queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent drift between code and docs. Classifies impact as no-change, in-place edit (one to a few paragraphs), or structural change (new page or TOC reshape), then orchestrates a CDO + doc-writer + python-architect + editorial-owner + growth-hacker loop to produce a patch-ready advisory. Does NOT review code quality, security, or test coverage. Does NOT auto-merge or auto-push doc edits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Queue open microsoft/apm pull requests (community fixes, PRs without an issue, or PRs that close an issue) and fan them out through an isolated pool (default 2) of autopilot-pr-triage-worker sessions. Advisory only. Never merges, never assigns, never requests reviewers, never runs autopilot-pr-review-worker. Activate on a mixed PR list or queue-open when the job is PR triage. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Queue microsoft/apm pull requests labelled `panel-review` (or an explicit named list) and fan them out through an isolated pool (default 2) of autopilot-pr-review-worker sessions. Advisory only. Never implements. Never composes autopilot-pr-merge-worker. Never review every open PR. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow. Does not triage issues or open greenfield PRs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to queue maintainer-accepted microsoft/apm issues (`status/accepted`) and fan them out through an isolated pool (default 2) of autopilot-issue-delivery-worker sessions. Any accepted type is eligible. Advisory `triage/recommended` is not authorization. Does not triage. Does not review PRs. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate data quality in market analysis documents and blog articles before publication. Use when checking for price scale inconsistencies (ETF vs futures), instrument notation errors, date/day-of-week mismatches, allocation total errors, and unit mismatches. Supports English and Japanese content. Advisory mode -- flags issues as warnings for human review, not as blockers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operate GJC SDK sessions from the CLI (`gjc sdk session list|inspect|send|status|tail|close|raw` plus the explicit raw control|query|global hatch). Advisory reference: broker-bound, credential-free output; mutating verbs run only when explicitly invoked.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Index of trusted GJC SDK reference guides (broker, session CLI, embedding, app development). Advisory only: read these documents for background; there is no guide to execute and no workflow skill to run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AWS security service suitability, coverage and cost recommendations: WAF/origin overlap, AWS Network Firewall inspection coverage and policy review, VPC endpoint, Transit Gateway/Cloud WAN segmentation and DNS Firewall security-control suitability, certificate renewal ownership and monitoring, incident response triage ownership, centralized security log store (CloudWatch or Security Lake). Also factual configuration, findings, data sources and severity scoring for GuardDuty, Inspector, Security Hub V2/OCSF (Exposure, connectors, automation), Security Hub CSPM/ASFF (standards, controls), Macie, Detective, Security Lake, AWS Security Incident Response membership and case coverage, and Organizations security policies. Applies to advisory security-service choices even when one service is named. Implementation, rule or code authoring, deployment, scans and troubleshooting outside these factual procedures belong to specialist skills. Supports local AWS CLI and AWS MCP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Score one blog post (or a folder of posts) on a 5-category 100-point scale covering content quality, SEO, E-E-A-T, technical elements, and AI citation readiness. Runs the deterministic analyzer first, then adds judgment and prioritized Critical/High/Medium/Low fixes. Advisory style diagnostics never infer authorship or affect the score. Exports markdown, JSON or table; works with MDX, markdown, HTML or a URL. Use when the user asks to analyze, score, rate or check the quality of specific posts ("analyze blog", "blog score", "check blog quality", "rate this post"). For a site-wide health check (orphan pages, cannibalization, stale content, schema across all posts) use blog-audit instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build safe, local, defensive reproductions of ALREADY-PATCHED, publicly disclosed security vulnerabilities (CVEs, vendor advisories, AI-agent incidents) for whitepapers, control testing, and education. Use this skill whenever the user wants to reproduce, demonstrate, or write up a known vulnerability or security incident — phrases like "reproduce this CVE", "build a repro for", "demonstrate the EchoLeak/Cursor/postmark-mcp issue", "show how this exploit worked", "add a reproducibility guide", or "pull the NVD/CVE details for". It fetches advisory metadata from NVD and CVE.org, confirms the issue is fixed, and produces a vulnerable-vs-patched harness that is offline, loopback-only, and uses synthetic markers. It NEVER discovers, develops, or weaponizes new zero-days and refuses any unpatched or live-target request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Project orchestrator for the screenwriting skill set (剧本项目主线调度 / 状态存档 / story bible) — a meta-skill that adds no new craft knowledge but routes a screenplay or stage-play project through stages (premise → structure → character → scenes → draft → revision → submission) and a TV / streaming series project (电视剧 / 剧集 / pilot / 一季) through a separate series stage table (engine → character network & season arc → documents/bible → pilot structure → break story & outline → draft → submission), names which sw-* skill to invoke at each stage, defines each stage's deliverable and advisory exit check, and keeps all project state in a story-bible.md file so work can resume across sessions. Use when starting a new script project, resuming one ("continue my screenplay", "where were we"), when the user asks "what should I do next" on a script, when converting a vague idea into a full development pipeline, or when the other sw-* skills are firing individually and the overall process needs sequencing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Land the winning experiment from an evo run as a clean, mergeable change -- open a PR when the repo has a remote, otherwise merge into the working branch. Distills the best-scoring experiment down to the minimal diff that reproduces its behaviour, shaped for the qualities a maintainer merges on (scope discipline, test integrity, style adherence), then attaches an advisory mergeability report. Use when the user invokes /evo:ship, asks to land/merge/ship the best result, or wants to turn a finished optimization into a pull request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.