interos

Guides safe operation of Interos supply-chain risk intelligence, graph analytics, and i-Score monitoring.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill interos-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interos
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/platforms/risk/interos
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill interos-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with Interos risk intelligence is dangerous in non-obvious ways: the graph is AI-modeled rather than attested, scores can be read on the wrong scale, and the real risk is sensitive sub-tier and sanctions data leaving the trust boundary. This Skill gives an AI agent the operator judgment to classify every Interos action by data sensitivity and egress, and to stop consequential actions for human approval. ## Core Features & Use Cases - Action classification by sensitivity and egress: Gates reads, watchlist writes, tenant-wide scorecard changes, graph curation, and cross-system pushes on a four-tier egress ladder instead of treating everything as a safe read. - Graph and score skepticism: Teaches verification of entity resolution, edge confidence, score direction (resilience vs risk), factor breakdowns, and feed freshness before acting on an i-Score or propagated alert. - Blind-spot and destructive-by-proxy protection: Prevents muting alerts or dropping watchlist entities to quiet noise, and hard-gates pushing risk flags into ERP/procurement systems that may auto-block suppliers. - Use Case: A user asks to email a shared-node concentration map to an outside consultant; the Skill classifies the payload as high-sensitivity egress, requires a named owner and approved destination, and defaults to blocking when the destination is unknown. ## Quick Start Ask the agent to assess a supplier's i-Score and concentration exposure in Interos and recommend whether any action should be gated for human approval.

Frequently Asked Questions about interos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely act on an Interos i-Score before making a sourcing decision?

Treat the i-Score as a modeled prior, not a verdict. Confirm the score direction (resilience vs risk), open the factor breakdown, check feed freshness, and corroborate before any irreversible action like de-sourcing or blocking a supplier.

What is the difference between Interos, Resilinc, and Everstream for supply-chain risk?

Interos is graph-first: one AI-modeled n-tier relationship graph with concentration analytics and continuous monitoring. Resilinc uses supplier-attested data like BCP and TTR, while Everstream ships separate Discover, Explore, and Reveal products.

Can I export Interos sub-tier graph or concentration data to external tools?

Only through a hard gate with a named owner and an approved destination. Sub-tier graphs, concentration maps, sanctions findings, and licensed feed values are the highest-sensitivity payloads and default to blocked when the destination is unknown.

Why is pushing an Interos risk flag into SAP MM dangerous?

The target system may auto-act on the flag, triggering vendor blocks or PO cancellations that are hard to unwind. Check the target's automation posture first; if unconfirmed, treat the push as destructive-by-proxy and hard-gate it.

What happens when I remove a supplier from an Interos watchlist?

Removing an entity stops its active alerts, creating a monitoring blind spot even though the graph still tracks it globally. A disruption during the gap costs lead time that cannot be recovered, so coverage-reducing writes require human approval.

When should Interos not be used for sanctions screening?

Interos flags restricted-party and forced-labor risk for investigation but does not adjudicate or block. Screening and block-and-release decisions belong in a compliance system of record such as SAP GTS with a human officer.