584건 · 관련도순
Helps startup leaders make strategic data decisions: assess permission to train AI on customer data, choose data architecture, evaluate customer data as a business asset, and sequence hiring around the decisions the business needs to make.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan customer retention and customer success staffing for a startup. Break down renewal and churn patterns, group customers by value and fit, and compare service models to guide resource allocation and hiring.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review changed test specifications for cases where broken behavior could still pass. Report concrete gaps supported by the changes and implementation, with a minimal fix and an observable condition for resolving each advisory finding.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Validate the staging NemoClaw Brev Launchable by checking its web deployment flow, environment access, deployed image, and preinstalled user journey. Report inference results and missing dependencies separately as advisory evidence outside automated end-to-end testing.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Handle network requests blocked by an OpenShell sandbox by checking its current access rules and proposing the smallest necessary change. Wait for approval and confirmation that the policy has reloaded before retrying the request.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Combine Convex authorization, code quality, performance, and failure audits into one readiness report. It removes duplicate findings, scores confirmed issues with a stated formula, and orders the fixes while clearly identifying checks that could not run.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review smart contract projects against Trail of Bits development guidelines. Examines architecture, upgrade mechanisms, implementation, dependencies, and tests, then provides system documentation, identifies gaps, and recommends improvements in priority order with code references.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design workflows where specialized AI agents share recurring product management tasks. Define each agent’s role, required information, handoffs, and human review points, then create monitoring and evaluation plans for the overall workflow.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan AWS architectures, compare services, and review security using documentation verified through AWS MCP tools, which connect agents to external information. Get implementation examples and trade-offs tailored to the team's existing tools, experience, and constraints.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Inspect a project's code, history, tests, and documentation, then ask three focused questions to recommend an AI-assisted development approach. Receive one combination of methods, reasons for the choice, and practical first steps tailored to the project.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Drive ONE already selected open pull request in microsoft/apm to mergeable. Classifies copilot-pull-request-reviewer[bot] inline review, runs autopilot-pr-review-worker, folds (by default) every recommendation inside the PR's stated scope, pushes to the head branch or a superseding PR that preserves authorship via commit trailers, watches CI to green (`agent-merge` when that skill or `<agent_merge_state>` is present; otherwise `gh pr checks --watch`), and iterates under fixed caps until ready-to-merge, advisory-with-deferred, superseded, or blocked. Plan before any fold, push, or reviewer request. Never spawned by autopilot-pr-review-scheduler. That scheduler is advisory only. Invoke this skill by name when the caller asked to drive a PR to merge.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. panel-mode (full | lean | delta) selects a surface-gated roster plus a CEO synthesizer; omitted or unknown mode is lean. Do not spawn inactive stubs. The orchestrator is the sole writer to the PR: ONE recommendation comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes follow-ups, and renders a ship-recommendation that the maintainer and author weigh.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-*.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/*.schema.json), or the conformance fixture seed (tests/fixtures/spec-conformance/**). The panel fans out to four spec-ecosystem reviewers (swagger-openapi-editor, oci-distribution-editor, pkgmgr-registry-contract-editor, w3c-tag-architect), each running in its own agent thread, and a spec-editor synthesizer that produces a fold-now / defer-v0.1.1 / defer-v0.2 / reject list plus a ship decision keyed off a 1..10 shocked_meter scale. The orchestrator is the sole writer to the PR: ONE consolidated comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes folds, and renders a ship recommendation that the maintainer weighs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
基于现有内容数据和画像迭代优化内容策略。分析过去一段时间的内容表现、画像信息、 行业趋势，给出下一阶段的内容方向调整、新赛道建议、内容形式优化、发布节奏调整、 画像微调等策略建议。当用户说"下一步怎么做"、"策略建议"、"怎么调整"、"内容方向"、 "下个月策略"、"优化建议"、"迭代方向"时触发。 和 skill-content-strategy 的区别：content-strategy 从零制定策略， strategy-advisor 基于现有数据做迭代优化。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[omh] Security event on the code already shipped -- a CVE in a dependency, a secret committed to the repo, a license question, an advisory: triage reachability and severity, contain in order, and never close a leaked secret before its rotation is observed. Use when the user says: security-event-response, security event response, cve, triage this cve, cve in our dependency, cve in a dependency, security advisory, dependabot alert.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[omh] Outside AI critique wanted: consulting an external advisor when configured. Use when the user says: ask, external advisor, ask claude, ask gemini, consult claude, consult gemini, opinion from claude, opinion from gemini.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AWS-curated copy-paste prompts for AI coding agents (MVP scaffolding, RAG chatbot with Claude on Bedrock, security baseline evaluation, cost anomaly detection, GPU quota requests, EKS deployment, Well-Architected review, etc.) plus downloadable installable agents (Multi-Account Transition Advisor, Bill Shock Preventer, Service Quota Agent, Bedrock Model Availability Agent, AWS DB Advisor). Use when the user asks for a prompt to do X on AWS, wants an installable agent for multi-account / cost monitoring / quota management / Bedrock model availability / database selection, or asks how to use AWS prompts. For migration intent (GCP to AWS, Azure to AWS, OpenAI/Gemini to Bedrock), route to the migration skills in this plugin (`gcp-to-aws`, `azure-to-aws`, `heroku-to-aws`, `llm-to-bedrock`). Do not use for: factual AWS Activate / programs / credits questions, learn articles, sample architectures, or for prompts that are not in the bundled `references/prompt-library/` tree.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Surfaces a single, genuinely relevant AWS Activate partner offer as optional context AFTER another AWS Startup Advisor skill has finalized its recommendation, plan, or build — never influencing the technical advice. Consulted by architect-for-startups, start-building-for-startups, agent-advisor, gcp-to-aws, heroku-to-aws, and llm-to-bedrock: once their output is final, this skill checks whether a relevant Activate offer exists for what the founder is building or migrating and, if so, appends one quiet, dismissible line with a tracked redeem link. Merit-first (offers never change the recommendation), relevance-gated to what the founder actually surfaced, at most one per response and often none, muteable. Offer content is read live from the sibling knowledge-base-for-startups skill (references/offers.md). Do NOT use for account-specific lookups (credits balance, Activate membership, application status) — send those to https://aws.amazon.com/startups.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recommend a data-portal architecture (storage, compute, catalog, access, hosting, metadata) from stated needs, then hand off to the build skills. The advisory entry point. Use when starting a new data-portal project and the underlying architecture has not yet been decided.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end methodology for reproducing AND patching publicly disclosed, already-fixed vulnerabilities: sourcing the advisory and the fix commit, reading the patch diff, rebuilding a pinned offline lab, building a vulnerable-vs-patched contrast harness with proper controls, minimizing the trigger, designing and validating the fix, and writing it up as a blog post or whitepaper. Use this skill whenever the user wants to reproduce, demonstrate, understand, teach, or write about a known vulnerability or security incident: "reproduce this CVE", "build a repro for", "how did EchoLeak / Log4Shell / the postmark-mcp package actually work", "show me how this exploit worked", "write a blog post about this vulnerability", "set up a lab for CVE-XXXX", "pull the NVD/CVE/OSV details", or "make a PoC I can publish". Use it just as eagerly for the patching half: "how should this be fixed", "is this patch correct", "what would have caught this", "review this security fix", "write a regression test for this CVE", "how do I backport this", or "what's the right fix for this bug class" - even when the user never says the word "reproduce". Reach for it on vague asks like "help me understand this security advisory", "I want to write about this incident", or "can we test whether we were vulnerable" when a disclosed vulnerability is in play. This skill only handles ALREADY-PATCHED, publicly disclosed issues and refuses zero-day discovery, live targets, and weaponization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks for a "GPT second opinion", wants a "cross-model review", needs to "check a plan before committing", wants another view after repeated failures, or explicitly invokes "codex-advisor".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.