{"id":21177,"plugin_id":"plugins_6aac006819508191a02506fb32a88714","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:16:50.618Z","digest":"2c228110e65ee00a366ae982c2462bf6e6ac835d1b0ea2ae54b23f6e89b7c89d","against":null,"payload":{"name":"enterprise-signal-ranking","description":"Rank weak and strong enterprise signals by executive relevance, impact, urgency, novelty, dependency reach and uncertainty. Use when the user needs enterprise signal ranking for CIO decision support.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":141}],"skill_md_contents":"---\nname: enterprise-signal-ranking\ndescription: Rank weak and strong enterprise signals by executive relevance, impact, urgency, novelty, dependency reach and uncertainty. Use when the user needs enterprise signal ranking for CIO decision support.\n---\n\n# Enterprise Signal Ranking\n\n## Mission\n\nTurn noisy updates into ranked executive signals.\n\n## Inputs\n\nAccept mixed updates, ticket trends, project notes, risk items, budget anomalies, security findings, stakeholder messages, meeting notes and KPI changes.\n\n## Workflow\n\n1. Extract discrete signals from the provided context.\n2. Score each signal by impact, urgency, novelty, dependency reach, confidence and actionability.\n3. Separate signal from noise.\n4. Identify weak signals that deserve monitoring.\n5. Recommend routing: command center, briefing, risk chain, action framework or memory.\n\n## Output Format\n\n- Executive Summary\n- Ranked Signals\n- Weak Signals to Monitor\n- Noise / Low-Value Items\n- Recommended Routing\n- Evidence & Assumptions\n- Missing Data\n\n## Guardrails\n\nDo not discard low-evidence signals if potential impact is severe. Route them to monitoring.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}