intelligence-analysis-techniques
Skill30 starsChanged 9 months agoApache-2.0View on GitHub
Structured analytic techniques including ACH, SWOT, Devil's Advocacy for EU parliamentary intelligence analysis
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Apply Structured Techniques: Use established analytic frameworks (ACH, SWOT, Key Assumptions Check, Indicators & Warnings) rather than …
- Distinctive: line 33
Update Continuously: Treat analysis as iterative — revise conclusions when new EP data becomes available through MCP Server queries
- Distinctive: line 107
Technique Without Data: Do NOT apply structured techniques as empty frameworks — each cell in an ACH matrix must reference verifiable EP …
- Distinctive: line 108
Single Technique Reliance: Do NOT rely on only one analytic method — combine ACH with Key Assumptions Check or SWOT to capture different …
- Distinctive: line 109
Confirmation Bias in Evidence Selection: Do NOT selectively include evidence that supports a preferred hypothesis — systematically query …
- Distinctive: line 110
False Precision: Do NOT assign precise probabilities to inherently uncertain political outcomes — use confidence bands and scenarios instead
- Distinctive: line 111
Static Analysis: Do NOT treat a one-time analysis as permanent — EU parliamentary dynamics shift with each plenary session, committee vote, …
- Distinctive: line 112
Ignoring Context: Do NOT analyze EP votes in isolation from broader EU institutional dynamics — Council positions, Commission proposals, …
- Distinctive: line 113
Overcomplicating Simple Questions: Do NOT apply heavyweight structured techniques when a straightforward data query answers the question — …
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Intelligence Analysis Techniques for EU Parliament
Context
This skill applies when:
- Performing structured analysis of EU legislative outcomes and political dynamics
- Evaluating competing hypotheses about MEP voting behavior or political group strategy
- Conducting SWOT analysis of political group positioning in the European Parliament
- Applying Devil's Advocacy to challenge assumptions about EU policy trajectories
- Using structured analytic techniques to reduce cognitive bias in parliamentary analysis
- Forecasting legislative procedure outcomes (first reading, conciliation, rejection)
- Assessing political coalition feasibility for specific policy dossiers
- Analyzing trilogue negotiation dynamics between EP, Council, and Commission
This skill supports evidence-based analysis aligned with Hack23 ISMS data integrity and quality requirements.
Rules
- Apply Structured Techniques: Use established analytic frameworks (ACH, SWOT, Key Assumptions Check, Indicators & Warnings) rather than intuitive judgment alone
- Evidence-Based Analysis: Ground all analytical conclusions in verifiable data from the EP MCP Server — cite specific votes, documents, and procedures
- Hypothesis Pluralism: Generate at least three competing hypotheses before evaluation — avoid anchoring on the first plausible explanation
- Cognitive Bias Mitigation: Actively counter confirmation bias, availability heuristic, and mirror imaging when analyzing MEP motivations and political group strategies
- Distinguish Fact from Inference: Clearly separate observed data (MEP voted "Yes" on dossier X) from analytical judgments (MEP supports policy direction Y)
- Confidence Levels: Assign and communicate confidence levels (low/medium/high) with supporting rationale for all analytical assessments
- Temporal Framing: Specify the time horizon of analysis — short-term (current plenary), medium-term (legislative term), long-term (institutional evolution)
- Document Analytical Process: Record the technique used, evidence considered, alternatives evaluated, and reasoning chain per ISMS audit requirements
- Update Continuously: Treat analysis as iterative — revise conclusions when new EP data becomes available through MCP Server queries
- Peer Review: Subject significant analytical products to Devil's Advocacy or Red Team challenge before final assessment
Examples
Analysis of Competing Hypotheses (ACH) for Legislative Outcome
Dossier: EU AI Act (2021/0106(COD))
Hypotheses:
H1: EP will adopt a strong regulatory framework (comprehensive rules)
H2: EP will adopt a light-touch approach (industry self-regulation)
H3: EP will fragment — no majority for any coherent position
Evidence Matrix (from MCP Server data):
+----------------------------------+----+----+----+
| Evidence | H1 | H2 | H3 |
+----------------------------------+----+----+----+
| IMCO/LIBE joint committee vote | ++ | -- | - |
| EPP rapporteur position | + | + | - |
| S&D amendment pattern | ++ | -- | - |
| ECR/ID opposition amendments | - | ++ | + |
| Renew bridging proposals | + | + | -- |
| Plenary amendment voting splits | + | - | + |
+----------------------------------+----+----+----+
Assessment: H1 most consistent with evidence (High confidence)
Key diagnostic: Joint committee vote margin and amendment patternsSWOT Analysis for Political Group Strategy
Subject: Renew Europe Group — EP10 Strategic Position
Strengths:
- Centrist positioning enables coalition flexibility (EPP or S&D)
- Strong presence in key committees (ECON, ITRE)
- Data source: get_meps (group filter), committee membership records
Weaknesses:
- Internal ideological diversity (liberal vs. centrist tensions)
- Smaller delegation size limits rapporteur assignments
- Data source: voting cohesion analysis from plenary roll-calls
Opportunities:
- Kingmaker role when EPP-S&D grand coalition insufficient
- Growing influence on digital/tech policy where group has expertise
- Data source: track_legislation filtered by policy area
Threats:
- National delegation losses in next EP elections
- Squeeze between consolidating EPP and growing Greens/EFA
- Data source: historical trend analysis across EP termsKey Assumptions Check
Assumption: "The EPP-S&D grand coalition will continue to dominate EP decision-making"
Check against EP MCP Server data:
1. Calculate grand coalition voting alignment rate per legislative term
2. Identify policy areas where grand coalition breaks down
3. Measure frequency of alternative majorities (EPP+Renew+ECR)
4. Track political group size trends across EP6–EP10
5. Assess impact of new political group formations
Diagnostic indicators that assumption may be failing:
- Grand coalition alignment drops below 60% on key votes
- Three or more alternative majority coalitions form per session
- Combined EPP+S&D seat share falls below 50%Anti-Patterns
- Technique Without Data: Do NOT apply structured techniques as empty frameworks — each cell in an ACH matrix must reference verifiable EP data
- Single Technique Reliance: Do NOT rely on only one analytic method — combine ACH with Key Assumptions Check or SWOT to capture different analytical dimensions
- Confirmation Bias in Evidence Selection: Do NOT selectively include evidence that supports a preferred hypothesis — systematically query MCP Server for both supporting and disconfirming data
- False Precision: Do NOT assign precise probabilities to inherently uncertain political outcomes — use confidence bands and scenarios instead
- Static Analysis: Do NOT treat a one-time analysis as permanent — EU parliamentary dynamics shift with each plenary session, committee vote, and trilogue round
- Ignoring Context: Do NOT analyze EP votes in isolation from broader EU institutional dynamics — Council positions, Commission proposals, and national elections all influence EP behavior
- Overcomplicating Simple Questions: Do NOT apply heavyweight structured techniques when a straightforward data query answers the question — use the right level of analytical effort
In this repository41 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- ai-development-governanceSkill
- ai-governanceSkill
- architecture-documentationSkill
- aws-security-architectureSkill
- behavioral-analysisSkill
- business-model-canvasSkill
- c4-architecture-documentationSkill
- code-quality-excellenceSkill
- compliance-frameworksSkill
- contribution-guidelinesSkill
- data-science-for-intelligenceSkill
- documentation-standardsSkill
- electoral-analysisSkill
- european-parliament-apiSkill
- european-political-systemSkill
- gdpr-complianceSkill
- github-actions-workflowsSkill
- github-agentic-workflowsSkill
- incident-responseSkill
- isms-complianceSkill
- legislative-monitoringSkill
- mcp-gateway-configurationSkill
- mcp-gateway-securitySkill
- mcp-server-developmentSkill
- open-source-governanceSkill
- osint-methodologiesSkill
- performance-optimizationSkill
- political-science-analysisSkill
- risk-assessment-frameworksSkill
- secrets-managementSkill
- secure-code-reviewSkill
- secure-development-lifecycleSkill
- security-by-designSkill
- seo-best-practicesSkill
- strategic-communication-analysisSkill
- testing-mcp-toolsSkill
- testing-strategySkill
- threat-modeling-frameworkSkill
- typescript-strict-patternsSkill
- vulnerability-managementSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

