osint-methodologies
Skill30 starsChanged 9 months agoApache-2.0View on GitHub
OSINT collection, source evaluation, data integration, and verification techniques for EU parliamentary intelligence
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
All OSINT activities must comply with Hack23 ISMS policies including data protection, access control, and ethical data handling …
- Very specific: line 25
Authoritative Sources First: Always prioritize EP Open Data Portal (data.europarl.europa.eu) via the MCP Server as the primary source — …
- Distinctive: line 28
Multi-Source Triangulation: Verify findings across at least two independent sources — cross-reference MCP Server data with EP official …
- Distinctive: line 30
GDPR-Compliant Collection: Only collect personal data with legal basis — MEP parliamentary activity is public, but private contact details …
- Distinctive: line 33
Attribution and Transparency: Always attribute data to its source.
- Distinctive: line 85
Single Source Reliance: Do NOT base conclusions on a single data source — even EP official data may have delays, errors, or incomplete …
- Distinctive: line 86
Bulk Personal Data Collection: Do NOT harvest MEP personal data beyond what is necessary for parliamentary accountability analysis — this …
- Distinctive: line 87
Unverified Attribution: Do NOT attribute positions to MEPs based solely on political group membership — verify individual voting records …
- Distinctive: line 88
Ignoring Data Staleness: Do NOT treat cached or historical data as current — always check retrieval timestamps and data freshness, …
- Distinctive: line 89
Conflating Public and Private: Do NOT mix MEP's official parliamentary activity (public OSINT) with private life information — maintain …
- Distinctive: line 90
Over-Collection: Do NOT collect data "just in case" — follow the collection plan and minimize data retention per GDPR data minimization …
- Distinctive: line 91
Ignoring Source Bias: Do NOT treat all sources as equivalent — media reports have editorial bias, advocacy organizations have policy …
≈ “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
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 papersMEP 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 timestampsLegislative 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 provenanceAnti-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
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
- intelligence-analysis-techniquesSkill
- isms-complianceSkill
- legislative-monitoringSkill
- mcp-gateway-configurationSkill
- mcp-gateway-securitySkill
- mcp-server-developmentSkill
- open-source-governanceSkill
- 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.

