1,517 件 ・ 関連度順
概要と使いどころ
Comprehensive Amazon profit analysis and revenue optimization. Revenue waterfall analysis, hidden fee identification, ACoS impact assessment, return cost calculation, and profitability optimization strategies. Use when the user asks about Amazon profit analysis, profitability calculation, fee analysis, margin optimization, or revenue breakdown.
日本語の概要は準備中です。原文の説明を表示しています。
Run a large-scale language migration with the six-step process: create the map and the rules, stress-test the rules, translate everything, compile, run it, match behavior. Use when the user wants to migrate, port, or rewrite a codebase from one language to another ("migrate this to Rust", "port our Python CLI to TypeScript", "should we rewrite this in Go?"), or asks for a migration feasibility assessment. Not for incremental JS→TS adoption — that needs no machinery — or single-file conversions.
日本語の概要は準備中です。原文の説明を表示しています。
First-tier tech company P7 capability advisor for evaluating, coaching, and giving career advice against a P7 technical/product/expert profile. Use when the user asks for P7-level assessment, promotion readiness, capability gaps, resume/project review, interview preparation, or concrete growth advice based on first-tier tech company P7 expectations.
日本語の概要は準備中です。原文の説明を表示しています。
First-tier tech company P8 capability advisor for evaluating, coaching, and giving career advice against a P8 senior expert, architect, or domain-owner profile. Use when the user asks for P8-level assessment, promotion readiness, capability gaps, project or resume review, interview preparation, or growth advice based on first-tier tech company P8 expectations.
日本語の概要は準備中です。原文の説明を表示しています。
First-tier tech company P9 capability advisor for evaluating, coaching, and giving career advice against a P9 senior expert, director, or business/organization-level leader profile. Use when the user asks for P9-level assessment, promotion readiness, executive capability gaps, strategic project review, resume positioning, interview preparation, or growth advice based on first-tier tech company P9 expectations.
日本語の概要は準備中です。原文の説明を表示しています。
Review dimensions and scoring for root cause analysis quality assessment
日本語の概要は準備中です。原文の説明を表示しています。
Type-specific validation checklists, six quality characteristics, and quality gate thresholds for documentation assessment
日本語の概要は準備中です。原文の説明を表示しています。
Requirements quality critique dimensions for peer review - confirmation bias detection, completeness validation, clarity checks, testability assessment, and priority validation
日本語の概要は準備中です。原文の説明を表示しています。
Critique dimensions, severity framework, verdict decision matrix, and review output format for documentation assessment reviews
日本語の概要は準備中です。原文の説明を表示しています。
Rollback procedures, risk assessment, pre/post-deployment validation, and contingency planning. Load when orchestrating deployment or preparing rollback plans. For deployment strategy details (canary, blue-green, rolling), see `cicd-and-deployment` skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized assessment of federated identity systems including SAML, OIDC, OAuth2 flows, SSO misconfiguration, and token confusion issues.
日本語の概要は準備中です。原文の説明を表示しています。
Use for software supply-chain security assessment covering SBOM, SCA, CI/CD pipelines, container images, build integrity, dependency provenance, and vulnerability reachability.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized security assessment of LLM applications and AI agents, including prompt injection, tool abuse, RAG exposure, memory poisoning, and model supply-chain risks.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized wireless security assessment including Wi-Fi capture, WPA handshake analysis, rogue AP detection research, and lab-only deauth testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized database security assessment covering PostgreSQL/MySQL/MSSQL/Mongo/Redis exposure, authz, UDF/command paths, and misconfiguration review.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized OT/ICS security assessment covering Purdue model zoning, PLC/SCADA exposure, industrial protocol discovery, and safe passive-first evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for a visual or UI quality review of frontend code that already shipped, or passes a phase number. Produces {phase_num}-UI-REVIEW.md with a graded 1-4 assessment across six pillars.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized security assessment of REST, GraphQL, WebSocket, or SOAP APIs, including discovery, authentication, authorization, rate-limit, and CI/CD testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.
日本語の概要は準備中です。原文の説明を表示しています。
Your education and edtech brain trust. 25 named personas across 7 cells covering learning science, curriculum design, AI tutoring, higher-ed strategy, edtech platforms, assessment, and workforce development.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates. Use when preparing an exercise or assessment plan before execution.
日本語の概要は準備中です。原文の説明を表示しています。
PTES-aligned penetration testing methodology for backend, frontend, and mobile. Provides attack taxonomy, exploit techniques per vulnerability class, and platform-specific test matrices. Use when executing pentest workflow, planning security assessments, mapping attack surfaces, or building threat models.
日本語の概要は準備中です。原文の説明を表示しています。
NIST SP 800-61r3-aligned incident triage that preserves evidence, separates analysis from authorization, and records status. Use for incident intake, severity assessment, containment readiness, or evidence preservation; not generic debugging or unscoped response.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a lesson plan, student-facing materials, and observation template. Load this skill BEFORE asking the teacher any clarifying question about grade, subject, topic, standard, or timing. Use when a K-12 teacher needs a math, ELA, science, or social studies lesson built from scratch — even if grade, subject, or topic isn't yet stated. Do NOT load for grading, a rubric, assessment feedback, a quiz, or a standards lookup — answer those directly. Triggers on explicit requests (lesson plan, mini-lesson, unit plan, daily plan) and implicit teacher intent: "I'm teaching long division to 5th graders," "need to teach photosynthesis tomorrow." Core signal: teacher needs new instructional content created. A new lesson that asks for differentiated, tiered, or leveled materials is still ONE planning request — this skill produces those materials inside the lesson package; do not also invoke k12-lesson-differentiation. Not for differentiating an existing lesson (use k12-lesson-differentiation) or passage rewrites.
日本語の概要は準備中です。原文の説明を表示しています。