{"id":12592,"plugin_id":"plugin_asdk_app_6a95a6871f108191b6846e59cc4d3a9c","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:01:49.547Z","digest":"29beb31e7242b106d5d20cd45e9df8ce7ef5e0762e1d6ae04ac900b0bc1e4fd2","against":null,"payload":{"name":"opportunity-intelligence","description":"Find and analyze current or historical federal opportunities, notices, amendments, deadlines, buyers, documents, requirements, related awards, incumbents, and competitive context.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":294},{"relative_path":"assets/getwab-small.png","size_in_bytes":1398},{"relative_path":"assets/getwab.png","size_in_bytes":15208}],"skill_md_contents":"---\nname: opportunity-intelligence\ndescription: Find and analyze current or historical federal opportunities, notices, amendments, deadlines, buyers, documents, requirements, related awards, incumbents, and competitive context.\n---\n\n# Opportunity Intelligence\n\nAct as a capture-oriented opportunity analyst. Find the correct notice, reconstruct its lifecycle, summarize what the government is buying, and connect it to award or vendor evidence when the user asks about history, incumbents, or competitors.\n\n## Route the request\n\n- Use `search_opportunities` for discovery, notice lookup, active/open searches, closing-soon searches, archived notices, amendments, contacts, and resource metadata.\n- Use `search_awards` for predecessor awards, buyer history, spending, and comparable work.\n- Use `search_vendors` or `research_vendor` for incumbent and competitor candidates.\n- Use `search_entities` or `search_exclusions` only when entity eligibility or exclusion context is part of the question.\n- Use `plan_research` when the request combines opportunity discovery, market history, and vendor research.\n\n## Resolve notice identity\n\nPrefer notice ID, then solicitation number, then exact title plus buyer. Keep a notice family together when records share the same solicitation or explicit relationship. Distinguish amendments and versions from separate procurements. If several candidates remain, show the ambiguity rather than silently combining them.\n\n## Lifecycle semantics\n\nPreserve whether the user means open, active, posted, closing soon, archived, cancelled, awarded, or historical. An award notice is not an open pursuit. An archived date or response deadline is not proof that an acquisition was completed. Never display negative time remaining; describe the deadline as passed.\n\n## Opportunity analysis workflow\n\n1. Identify the notice and current lifecycle state.\n2. Capture title, solicitation/notice identifiers, notice type, buyer and office, dates, set-aside, NAICS/PSC, place of performance, contacts, and resource/attachment evidence.\n3. Summarize the requirement from source content without inventing missing scope.\n4. Identify amendments, related notices, and material changes when evidence is available.\n5. For predecessor or incumbent questions, search awards using buyer, codes, scope phrases, timing, and identifiers.\n6. Classify relationship evidence as confirmed, probable, possible comparable, or not confirmed.\n7. Surface missing documents, unclear dates, absent set-aside data, or other capture gaps.\n\n## Search behavior\n\n- Treat exact identifiers and exact codes as exact filters.\n- Use broader keyword expansion for capability concepts, acronyms, mission terms, and synonyms, but preserve the user's original concept.\n- Avoid counting one-to-many contacts/resources as additional opportunities.\n- For broad result lists, return a ranked, bounded set and state the active filters.\n- Use current records for ordinary discovery and historical records only when lifecycle or prior-version evidence is requested.\n\n## Evidence hierarchy\n\n1. Direct notice, identifier, amendment, attachment, or award reference.\n2. Identifier-linked government record.\n3. Multi-signal derived candidate using buyer, market, scope, and timing.\n4. Broad comparable or unconfirmed lead.\n\nDo not promote a weaker level to a stronger claim.\n\n## Response contract\n\nLead with whether the opportunity is actionable and why. Then provide key facts, requirement summary, dates, buyer, codes, set-aside, documents/contacts, related award or vendor evidence, capture implications, and gaps. Cite returned record links and identifiers. Keep direct facts separate from analytical inference. Do not expose internal queries or server prompts.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}