OSINT Methodologies for EU Parliamentary Intelligence
Context
This skill applies when:
- Collecting open-source intelligence from European Parliament public datasets
- Evaluating reliability of EU parliamentary data sources and cross-referencing records
- Integrating data from EP Open Data Portal with complementary EU institutional sources
- Verifying MEP activity claims against official parliamentary records
- Tracking legislative procedures across EP committees, plenary, and Council negotiations
- Building comprehensive MEP profiles from publicly available parliamentary data
- Monitoring political group dynamics using structured open-source collection
- Supporting transparency and accountability research on EU legislative processes
All OSINT activities must comply with Hack23 ISMS policies including data protection, access control, and ethical data handling requirements.
Rules
- Authoritative Sources First: Always prioritize EP Open Data Portal (
data.europarl.europa.eu) via the MCP Server as the primary source — supplement with EUR-Lex, Council Register, and Commission databases
- Source Evaluation (CRAAP): Assess each source for Currency, Relevance, Authority, Accuracy, and Purpose — EP official records score highest; media reporting requires corroboration
- Structured Collection Plan: Define collection requirements before querying — specify target MEPs, time periods, policy areas, and political groups to avoid data overload
- Multi-Source Triangulation: Verify findings across at least two independent sources — cross-reference MCP Server data with EP official website, VoteWatch Europe, and national parliament records
- Data Provenance Tracking: Record the source, retrieval date, and API endpoint for every data point — maintain audit trails per ISMS requirements
- GDPR-Compliant Collection: Only collect personal data with legal basis — MEP parliamentary activity is public, but private contact details and personal life data require GDPR justification
- Timeliness Classification: Tag data with temporal validity — plenary votes are permanent record, committee compositions change each term, MEP contact details change frequently
- Minimize Collection Footprint: Collect only data required for the analytical objective — avoid bulk harvesting of personal data beyond parliamentary functions
- Attribution and Transparency: Always attribute data to its source; never present compiled OSINT as original analysis without citing underlying records
- Ethical Boundaries: OSINT supports democratic transparency — never use parliamentary data for harassment, doxxing, or unauthorized surveillance of MEPs
Examples
EP Data Source Hierarchy
Tier 1 (Primary/Authoritative):
- EP Open Data Portal API (via MCP Server tools: get_meps, get_voting_records, search_documents)
- EUR-Lex (EU legislation full text)
- EP Legislative Observatory (procedure tracking)
Tier 2 (Official/Complementary):
- Council of the EU document register
- European Commission consultations and impact assessments
- EP Think Tank (EPRS) publications and briefings
Tier 3 (Structured Secondary):
- VoteWatch Europe (processed voting data)
- MEP personal websites and social media (declared positions)
- National parliament records (pre-EP career data)
Tier 4 (Media/Unstructured):
- EU-focused media (Politico Europe, EUobserver, Euractiv)
- National media in MEP's home country
- Academic publications and research papers
MEP Activity Verification
To verify an MEP's claimed legislative activity:
1. Query MCP Server: get_meps with MEP identifier
2. Cross-reference with get_voting_records for votes and get_plenary_sessions for speeches
3. Check committee membership and rapporteur assignments
4. Verify attendance patterns against official EP attendance records
5. Compare self-reported activity with EP roll-call vote participation rate
6. Document discrepancies with source citations and timestamps
Legislative Procedure Tracking
Track EU legislative dossier through institutional lifecycle:
1. Use track_legislation to identify the dossier reference (e.g., 2023/0079(COD))
2. Map committee responsible and committees for opinion
3. Track amendments: committee stage → plenary stage → trilogue
4. Cross-reference Council general approach with EP position
5. Monitor conciliation committee outcomes if applicable
6. Record all data points with EP Open Data Portal provenance
Anti-Patterns
- Single Source Reliance: Do NOT base conclusions on a single data source — even EP official data may have delays, errors, or incomplete records
- Bulk Personal Data Collection: Do NOT harvest MEP personal data beyond what is necessary for parliamentary accountability analysis — this violates GDPR and ISMS policies
- Unverified Attribution: Do NOT attribute positions to MEPs based solely on political group membership — verify individual voting records and stated positions
- Ignoring Data Staleness: Do NOT treat cached or historical data as current — always check retrieval timestamps and data freshness, especially for committee compositions
- Conflating Public and Private: Do NOT mix MEP's official parliamentary activity (public OSINT) with private life information — maintain strict boundaries
- Over-Collection: Do NOT collect data "just in case" — follow the collection plan and minimize data retention per GDPR data minimization principles
- Ignoring Source Bias: Do NOT treat all sources as equivalent — media reports have editorial bias, advocacy organizations have policy agendas, and even official records may reflect institutional framing
1---2name: osint-methodologies3description: OSINT collection, source evaluation, data integration, and verification techniques for EU parliamentary intelligence4license: MIT5metadata:6 source: https://skillmd.com/skills/hack23/osint-methodologies7---89# OSINT Methodologies for EU Parliamentary Intelligence1011## Context1213This skill applies when:14- Collecting open-source intelligence from European Parliament public datasets15- Evaluating reliability of EU parliamentary data sources and cross-referencing records16- Integrating data from EP Open Data Portal with complementary EU institutional sources17- Verifying MEP activity claims against official parliamentary records18- Tracking legislative procedures across EP committees, plenary, and Council negotiations19- Building comprehensive MEP profiles from publicly available parliamentary data20- Monitoring political group dynamics using structured open-source collection21- Supporting transparency and accountability research on EU legislative processes2223All OSINT activities must comply with [Hack23 ISMS policies](https://github.com/Hack23/ISMS-PUBLIC) including data protection, access control, and ethical data handling requirements.2425## Rules26271. **Authoritative Sources First**: Always prioritize EP Open Data Portal (`data.europarl.europa.eu`) via the MCP Server as the primary source — supplement with EUR-Lex, Council Register, and Commission databases282. **Source Evaluation (CRAAP)**: Assess each source for Currency, Relevance, Authority, Accuracy, and Purpose — EP official records score highest; media reporting requires corroboration293. **Structured Collection Plan**: Define collection requirements before querying — specify target MEPs, time periods, policy areas, and political groups to avoid data overload304. **Multi-Source Triangulation**: Verify findings across at least two independent sources — cross-reference MCP Server data with EP official website, VoteWatch Europe, and national parliament records315. **Data Provenance Tracking**: Record the source, retrieval date, and API endpoint for every data point — maintain audit trails per ISMS requirements326. **GDPR-Compliant Collection**: Only collect personal data with legal basis — MEP parliamentary activity is public, but private contact details and personal life data require GDPR justification337. **Timeliness Classification**: Tag data with temporal validity — plenary votes are permanent record, committee compositions change each term, MEP contact details change frequently348. **Minimize Collection Footprint**: Collect only data required for the analytical objective — avoid bulk harvesting of personal data beyond parliamentary functions359. **Attribution and Transparency**: Always attribute data to its source; never present compiled OSINT as original analysis without citing underlying records3610. **Ethical Boundaries**: OSINT supports democratic transparency — never use parliamentary data for harassment, doxxing, or unauthorized surveillance of MEPs3738## Examples3940### EP Data Source Hierarchy41```42Tier 1 (Primary/Authoritative):43 - EP Open Data Portal API (via MCP Server tools: get_meps, get_voting_records, search_documents)44 - EUR-Lex (EU legislation full text)45 - EP Legislative Observatory (procedure tracking)4647Tier 2 (Official/Complementary):48 - Council of the EU document register49 - European Commission consultations and impact assessments50 - EP Think Tank (EPRS) publications and briefings5152Tier 3 (Structured Secondary):53 - VoteWatch Europe (processed voting data)54 - MEP personal websites and social media (declared positions)55 - National parliament records (pre-EP career data)5657Tier 4 (Media/Unstructured):58 - EU-focused media (Politico Europe, EUobserver, Euractiv)59 - National media in MEP's home country60 - Academic publications and research papers61```6263### MEP Activity Verification64```65To verify an MEP's claimed legislative activity:661. Query MCP Server: get_meps with MEP identifier672. Cross-reference with get_voting_records for votes and get_plenary_sessions for speeches683. Check committee membership and rapporteur assignments694. Verify attendance patterns against official EP attendance records705. Compare self-reported activity with EP roll-call vote participation rate716. Document discrepancies with source citations and timestamps72```7374### Legislative Procedure Tracking75```76Track EU legislative dossier through institutional lifecycle:771. Use track_legislation to identify the dossier reference (e.g., 2023/0079(COD))782. Map committee responsible and committees for opinion793. Track amendments: committee stage → plenary stage → trilogue804. Cross-reference Council general approach with EP position815. Monitor conciliation committee outcomes if applicable826. Record all data points with EP Open Data Portal provenance83```8485## Anti-Patterns8687- **Single Source Reliance**: Do NOT base conclusions on a single data source — even EP official data may have delays, errors, or incomplete records88- **Bulk Personal Data Collection**: Do NOT harvest MEP personal data beyond what is necessary for parliamentary accountability analysis — this violates GDPR and ISMS policies89- **Unverified Attribution**: Do NOT attribute positions to MEPs based solely on political group membership — verify individual voting records and stated positions90- **Ignoring Data Staleness**: Do NOT treat cached or historical data as current — always check retrieval timestamps and data freshness, especially for committee compositions91- **Conflating Public and Private**: Do NOT mix MEP's official parliamentary activity (public OSINT) with private life information — maintain strict boundaries92- **Over-Collection**: Do NOT collect data "just in case" — follow the collection plan and minimize data retention per GDPR data minimization principles93- **Ignoring Source Bias**: Do NOT treat all sources as equivalent — media reports have editorial bias, advocacy organizations have policy agendas, and even official records may reflect institutional framing