{"id":73111,"plugin_id":"plugin_asdk_app_6ac993a96fe48191856f4963feaf3f20","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-31T01:18:22.229Z","digest":"9c0bd8a2a49e97795d05885d7c1bc4c78aed1a05fe6098202fcc9b1b3dc377fa","against":null,"payload":{"description":"This skill should be used when a user asks to research a company in public records, assemble an entity timeline, inspect a cross-source dossier, or find material events with dated source citations.","included_files":[],"name":"public-records-research","skill_md_contents":"---\nname: public-records-research\ndescription: This skill should be used when a user asks to research a company in public records, assemble an entity timeline, inspect a cross-source dossier, or find material events with dated source citations.\n---\n\n# Public records research\n\nBuild a source-linked, institution-level account from MORVS public datasets. Treat a name match as a lead until an identifier and underlying record support it.\n\n## Workflow\n\n1. Define the organization, jurisdiction, period, and question. Avoid collecting or repeating personal identifiers, residential addresses, or other PII. Report institution-level facts.\n2. Call `resolve` with exactly one known identifier when possible: `{\"ticker\":\"PFE\"}`, `{\"cik\":\"0000078003\"}`, or `{\"q\":\"Pfizer\"}`. Inspect canonical name, aliases, identifiers, available sources, and source links. Disambiguate similar names before proceeding.\n3. Select the narrowest useful tool:\n   - `entity_timeline` with `{\"key\":\"PFE\",\"days\":180,\"limit\":100}` for a dated cross-source event sequence. The key accepts ticker, CIK, UEI, LEI, DUNS, or numeric entity ID; maximum days is 730.\n   - `entity_material_events` with `{\"key\":\"PFE\",\"days\":180}` for the high-signal subset. Its importance threshold is a MORVS selection rule, not an official finding.\n   - `dossier` with `{\"ticker\":\"PFE\"}` or `{\"name\":\"Pfizer\"}` for the cross-topic overview.\n   - `company_profile` with `{\"ticker_or_cik\":\"PFE\"}` for an SEC-filing company profile. Do not use its absence to infer that a private organization has no records.\n4. Check the returned period, per-source coverage, record dates, and source links. Call `dataset_freshness` with `{}` if using a federal hub dataset and match its row to the dataset; distinguish source-observation time from indexed-content watermark. Mark unknown or stale coverage plainly. A missing hit is not evidence of no activity.\n5. Open the primary record URL for material claims when available. Distinguish a filing, complaint, press release, recall, contract, and agency finding. State only what the source establishes. Never turn a mention, allegation, or automated flag into an accusation.\n6. Return a short answer followed by a record table. Give access date and source date; omit a claim when no verifiable record URL is available.\n\n| Event or fact date | Institution-level finding | Dataset and source | Record ID | Primary record URL | Coverage or freshness |\n|---|---|---|---|---|---|\n| Use the record's date | State only the supported fact | Name the agency and MORVS index | If supplied | Link to the exact record | State the source window and any gap |\n\n## Worked examples\n\n**A public company's recent regulatory history.** For “What happened at Pfizer over the last six months?”, call `resolve` with `{\"ticker\":\"PFE\"}`, then `entity_timeline` with `{\"key\":\"PFE\",\"days\":180,\"limit\":100}` and `entity_material_events` with `{\"key\":\"PFE\",\"days\":180}`. Use `company_profile` with `{\"ticker_or_cik\":\"PFE\"}` only if financial and SEC context matters. Reconcile duplicates by record ID and date; cite each original filing or agency record. Do not infer misconduct from a high importance score.\n\n**An ambiguous organization name.** For “Research Acme Health”, call `resolve` with `{\"q\":\"Acme Health\"}`. Present candidate organizations and identifiers if more than one appears. After a verified match, call `dossier` with the exact organization name and `entity_timeline` with its returned identifier. If no identifier resolves, give only clearly attributed search leads and say the match is unconfirmed.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}