us-iran-war-tracker

A specialized skill for tracking the US-Iran conflict, strictly focusing on intelligence published within the **last 6 hours**. Use this for hyper-current, t...

Security Scan

The skill is internally coherent: its instructions match the stated purpose (near‑real‑time tracking of the US–Iran conflict), it requests no credentials or installs, and it does not instruct the agent to access unrelated system resources.

Purpose & Capability

Name/description align with SKILL.md. The skill is focused on 6‑hour, real‑time monitoring and lists expected search keywords, sources, and reporting structure. There are no unrelated environment variables, binaries, or config paths requested.

Instruction Scope

Instructions are narrowly scoped to web searches, source triage, and structured reporting (triangulation, tiered sources, 6‑hour rolling timeline). The SKILL.md does not instruct the agent to read local files, access credentials, or send data to third‑party endpoints other than public news and official websites. However, the skill gives broad discretion on search queries, languages, and verification steps without specifying which browsing/translation tool or API to use — that could cause the agent to use any available web/browsing capability.

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing is written to disk or fetched at install time.

Credentials

No environment variables, credentials, or config paths are requested. The lack of required secrets is proportionate to the stated purpose (public-source intelligence aggregation).

Persistence & Privilege

The skill does not request always:true and is user‑invocable. Model invocation is enabled by default (normal). Be aware that autonomous periodic monitoring combined with browsing could increase risk of unwanted autonomous data collection — but that risk stems from agent policy/configuration rather than the skill itself.

Assessment

This skill is coherent and technically low‑risk (no installs or secrets). Before installing: 1) Confirm which browsing/translation tool the agent will use and whether that tool has network access or will store logs. 2) Consider disabling or restricting autonomous invocation if you don't want the agent to run continuous monitoring without prompts. 3) Understand content risks: the domain involves heavy disinformation and graphic material — require strict triangulation and prefer Tier‑2/3 reputable outlets before acting on information. 4) If you use this in a sensitive environment, document legal/ethical limits on collection/redistribution of real‑time conflict intelligence. 5) No credentials are required; do not add unrelated credentials to the skill. If you want a higher assurance review, provide details on the agent's browsing plugin or runtime so its network/storage behavior can be audited.

US-Iran War Situation Tracker Skill

This skill provides a focused methodology for gathering and verifying real-time intelligence on the US-Iran conflict. It is tailored to navigate the specific information landscape of this war, prioritizing actionable intelligence over general news.

Core Principle: Assume Disinformation & Triangulate

In this high-stakes conflict, all primary sources (both US/allies and Iran/allies) have a strong agenda. Information should only be considered credible after triangulation: corroboration by sources from an opposing side or confirmation by a reputable, neutral third party (like a major news agency).

3-Step Intelligence Cycle for the US-Iran War

Step 1: Define Intelligence Needs & Specific Keywords

A strict 6-hour time filter is mandatory for all searches. This skill is for near-real-time tracking, not historical analysis.

Entity & Event Keywords:

• Involved Parties: US military, CENTCOM, Iranian Revolutionary Guard Corps (IRGC), Israel Defense Forces (IDF), Hezbollah, Houthi
• Geographic Locations: Persian Gulf, Strait of Hormuz, Red Sea, Indian Ocean, Tehran, Tel Aviv, Ali Al Salem Air Base (Kuwait), Jordan
• Military Hardware & Operations: IRIS Dena, Thaad system, ballistic missile, suicide drone, F-35, torpedo attack, cyber attack
• Key Personnel: Pete Hegseth (US Secretary of Defense), Abbas Araghchi (Iranian Foreign Minister)

Search Query Strategy:

• Action-Specific: (US OR American) AND (sinks OR strikes OR hits) AND (Iran OR Iranian) AND (ship OR vessel OR submarine)
• Location-Specific: (Iran OR Iranian) AND (missile OR drone) AND (attack OR strike) AND (Israel OR Tel Aviv)
• Official Statements: site:defense.gov "Iran", site:en.mfa.ir "United States", site:idf.il "Iran"
• Multi-lingual: Search key terms in English, Farsi (جنگ ایران و آمریکا), and Hebrew (מלחמת איראן-ארצות הברית) to capture local perspectives.

Step 2: Consult Tiered Authoritative Sources for This Conflict

Prioritize sources based on their proximity to the events and their established neutrality.

Tier	Source Type	Specific Examples for This Conflict	Purpose & How to Use
1A	US & Allies Primary Sources	defense.gov, centcom.mil, idf.il, state.gov	For official US/Israeli claims, statements, and footage. Treat as a claim to be verified.
1B	Iran & Allies Primary Sources	en.mfa.ir, IRNA.ir, Tasnim News Agency, Press TV	For official Iranian/allied claims and counter-claims. Treat as a claim to be verified.
2	Global News Agencies	Reuters, Associated Press (AP), AFP	Crucial for triangulation. These agencies often have correspondents on the ground and are the first to provide independently verified reports. Use them to confirm or deny claims from Tier 1 sources.
3	Specialized & International Media	Al Jazeera, BBC News, The Guardian, New York Times	For in-depth analysis, context, and reports on secondary effects (e.g., civilian casualties, diplomatic efforts). Good for understanding the "why" behind the "what."
4	International & Humanitarian Orgs	un.org (UN News), icrc.org (Red Cross), amnesty.org	For information on civilian impact, human rights, and potential war crimes.

Step 3: Synthesize & Report with Attribution

When presenting the findings, structure is key to clarity.

1. Lead with Verified Facts: Start with information confirmed by Tier 2 sources or acknowledged by both sides.
2. Present Competing Claims: Clearly separate uncorroborated claims, attributing them properly. Use phrasing like: "The US military claimed... while Iran's state media reported..." or "According to a statement from the IDF..."
3. Structure by Theme: Organize the report into logical sections:
   • Key Military Developments (Verified)
   • Official Statements & Claims (US/Allies)
   • Official Statements & Claims (Iran/Allies)
   • Civilian & Humanitarian Impact
   • International Reactions
4. Maintain a 6-Hour Rolling Timeline: Keep a running, time-stamped log of major events. This helps track escalation and the sequence of actions and reactions.