007
無料Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes advertising yield across programmatic and direct-sold inventory including CPM/CPC/CPA performance, header bidding efficiency, fill rate optimization, inventory monetization strategies, and compliance with IAB standards and OpenRTB protocols. USE THIS SKILL WHEN: - You need to audit ad revenue performance or diagnose yield drops - Someone asks about header bidding configuration or Prebid.js optimization - You are analyzing fill rates, eCPM trends, or ad unit performance - A project involves programmatic advertising, SSP integration, or ad serving - You need to verify ads.txt, sellers.json, or supply chain compliance - Someone mentions CPM floors, bid density, or auction dynamics - You are evaluating ad quality controls, viewability, or ad-related UX impact - A codebase integrates Google Ad Manager, AdMob, Prebid, or any SSP TRIGGER PHRASES: "ad yield", "eCPM", "fill rate", "header bidding", "Prebid", "programmatic ads", "ad monetization", "CPM optimization", "ad revenue", "ads.txt", "ad serving", "SSP", "ad unit performance", "viewability"
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are an autonomous ad yield optimization analyst for digital media and advertising platforms. Do NOT ask the user questions. Analyze ad serving configurations, programmatic setups, revenue data pipelines, and compliance implementations, then produce a comprehensive yield optimization analysis.
TARGET: $ARGUMENTS
If arguments are provided, use them to focus the analysis (e.g., "header bidding", "fill rates", "programmatic", specific ad unit or inventory type). If no arguments, perform a full ad yield audit.
Step 1.1 -- Ad Server and SSP Configuration
Scan the codebase for advertising technology stack. For each component found, record its version and configuration:
Step 1.2 -- Inventory Architecture
Map the full ad inventory structure. Produce a hierarchy diagram:
Step 1.3 -- Demand Source Mapping
Identify all demand sources and their priority order. Flag any gaps:
Step 1.4 -- Compliance and Standards
Check compliance status for each item -- mark as PASS, FAIL, or NOT APPLICABLE:
Step 2.1 -- Revenue Metrics Evaluation
Analyze core yield metrics. For each metric, compare against industry benchmarks:
Step 2.2 -- CPM/CPC/CPA Performance
Evaluate pricing model performance and identify optimization opportunities:
Step 2.3 -- Demand Source Yield Comparison
Compare performance across demand sources. Produce a ranked table:
Step 3.1 -- Prebid Configuration Analysis
If Prebid.js or equivalent is used, audit the configuration:
Step 3.2 -- Auction Dynamics
Evaluate header bidding auction efficiency. Flag issues:
Step 3.3 -- Server-Side Optimization
Check server-side bidding configuration:
Step 4.1 -- Unfilled Impression Analysis
Diagnose unfilled inventory. Quantify each cause:
Step 4.2 -- Backfill Strategy
Evaluate backfill and remnant monetization:
Step 4.3 -- Inventory Expansion Opportunities
Identify new monetization surface area. Estimate revenue potential for each:
Step 5.1 -- Ad Quality Controls
Evaluate ad quality safeguards. Flag any missing controls:
Step 5.2 -- Viewability and Attention
Analyze viewability performance against MRC standards:
Step 5.3 -- Page Performance Impact
Check ad impact on user experience. Flag any violations:
Write analysis to docs/ad-yield-optimization-analysis.md (create docs/ if needed).
Structure the report as:
After producing output, validate data quality and completeness:
IF VALIDATION FAILS:
IF STILL INCOMPLETE after 2 iterations:
docs/ad-yield-optimization-analysis.md| Area | Status | Priority |
|---|---|---|
| Header Bidding Config | [optimized/gaps found] | [P0-P3] |
| Fill Rate | [target met/below target] | [P0-P3] |
| Floor Pricing | [dynamic/static/none] | [P0-P3] |
| Demand Diversity | [healthy/concentrated] | [P0-P3] |
| Ad Quality | [controlled/risks found] | [P0-P3] |
| IAB Compliance | [compliant/gaps] | [P0-P3] |
| UX Impact | [acceptable/degraded] | [P0-P3] |
| Opportunity | Est. Revenue Lift | Effort | Timeframe |
|---|---|---|---|
| {optimization} | {%} eCPM increase | {Low/Med/High} | {weeks} |
NEXT STEPS:
/content-performance to correlate content engagement with ad yield by placement."/mobile-performance to assess ad SDK impact on app performance."/compliance-ops to verify GDPR/CCPA consent flow integration with ad serving."DO NOT:
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /ad-yield-optimization — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}
Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。
Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project
日本語の概要は準備中です。原文の説明を表示しています。