007
無料Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
日本語の概要は準備中です。原文の説明を表示しています。
Turn public agenda, news, policy moves, geopolitical developments, sanctions, trade disputes, regulation, elections, diplomatic signals, and strategic-risk events into decision-ready briefs. Use when the user asks an agent to analyze what changed, why it matters, who is affected, what is uncertain, scenarios, watch-next indicators, or risk implications instead of producing a simple news summary.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill to convert messy public agenda into decision-useful analysis.
Do not summarize the news by default. Identify the delta: what changed, who gained or lost leverage, what incentives shifted, what remains uncertain, and what the user should watch or decide.
Read only the smallest needed subset:
references/analysis-protocol.md — default reasoning protocol for agenda analysis.references/agenda-triage.md — classify developments as noise, weak signal, signal, structural shift, or trigger event.references/evidence-discipline.md — source handling, uncertainty labels, and live-verification limits.references/output-patterns.md — compact brief, decision memo, red-team, and watchlist formats.references/regional/central-asia-caspian.md — regional lens for Central Asia and Caspian agenda analysis.references/regional/middle-east.md — regional lens for Middle East agenda analysis.references/regional/eu.md — regional lens for European Union agenda analysis.references/sector/sanctions.md — sector lens for sanctions and export-control agenda analysis.For normal agenda questions, read analysis-protocol.md and agenda-triage.md.
For source-sensitive or current-event tasks, also read evidence-discipline.md.
For a requested format, read output-patterns.md.
For Central Asia, Caspian, sanctions-routing, corridor, banking, energy, minerals, or regional political-economy questions, also read references/regional/central-asia-caspian.md.
For Middle East, Gulf, Iran, Israel/Palestine, Red Sea, energy, maritime chokepoint, sovereign capital, sanctions, or escalation questions, also read references/regional/middle-east.md.
For European Union, EU regulation, sanctions, trade defense, digital regulation, climate policy, enlargement, competition, market access, or enforcement questions, also read references/regional/eu.md.
For sanctions, export controls, designations, delistings, enforcement, beneficial ownership, routing, financial restrictions, licenses, or compliance exposure, also read references/sector/sanctions.md.
Separate:
Never make speculation sound like fact. Never imply live verification if none was performed.
Use this compact shape unless the user requests otherwise:
**Bottom line:** ...
**Signal classification:** noise / weak signal / signal / structural shift / trigger event
**What changed:** ...
**Why it matters:** ...
**Who is affected:** ...
**Main uncertainty:** ...
**Scenarios:** ...
**Watch next:** ...
A good answer is shorter than a news recap and more useful than a generic think‑tank paragraph.
Cut:
Add the skill to your workspace (e.g. clawhub install agenda-intelligence). Then invoke it from a prompt:
[skill:agenda-intelligence]
Analyze the latest EU regulation on AI‑risk assessments. Identify what changed, who gains leverage, remaining uncertainties, and watch‑next indicators.
OpenClaw-style agents can load the referenced markdown files and use the CLI for validation, source plans, and before/after scoring. The exact runtime wrapper depends on the host agent environment.
You can also pass a brief directly:
[skill:agenda-intelligence]
Brief: "EU AI Act amendment 2026 – new high‑risk AI categories and tighter reporting thresholds."
Use this as an analysis request plus source-plan trigger. Automated source
fetching from a brief is not implemented yet; if live retrieval is unavailable,
mark the evidence mode as reasoning_only, user_provided, or mixed.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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
日本語の概要は準備中です。原文の説明を表示しています。