resilinc

Guides safe operation of Resilinc supply-chain risk intelligence with egress-aware action gating.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working with Resilinc's supplier risk intelligence is risky in a different way than ERP or warehouse systems: the danger is not posting money or stock, but leaking sensitive supplier-attested data (sub-tier maps, BCP plans, emergency contacts) or acting irreversibly on probabilistic scores and unconfirmed alerts. This Skill gives an AI agent the operator judgment to classify every Resilinc action by data sensitivity and egress, and to pause consequential ones for human approval. ## Core Features & Use Cases - Egress-aware action classification: Gates operations by payload sensitivity (aggregate vs named-supplier vs BCP/PII/bulk export) rather than simple read/write, with a hard gate for data that cannot be recalled. - Score and map literacy: Explains Resiliency Score vs RiskShield (opposite directions), TTR/TTS exposure gaps, Revenue-at-Risk, and why supplier-attested data is a claim, not an audit. - Cross-system push safety: Treats pushing a Resilinc risk flag into ERP/procurement systems as potentially destructive-by-proxy when the target auto-acts on it. - Use Case: A user asks to email a named supplier's BCP recovery plan to their procurement team. The Skill classifies the payload as highest-sensitivity, applies a hard gate requiring a named owner, and suggests a de-identified summary instead. ## Quick Start Ask the agent to assess a supplier's risk in Resilinc, for example: "Check the Resiliency Score and TTR/TTS exposure for our top chip suppliers and flag any single points of failure."

Frequently Asked Questions about resilinc

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

FAQPage Schema
How do I safely share Resilinc supplier risk data with my team?

Classify the payload first: aggregate or de-identified summaries need only audience confirmation, while named-supplier scores, sub-tier maps, BCP plans, or emergency contacts require an approved destination and named-owner sign-off. Bulk exports of sensitive data are gated hardest because egress cannot be recalled.

What is the difference between Resilinc Resiliency Score and RiskShield?

The Resiliency Score measures how prepared and recoverable a supplier is, where higher means more resilient. RiskShield measures risk categories like financial, ESG, cyber, and restricted-party exposure, where higher means more risk. Reading one on the other's scale inverts the decision.

When should I use Resilinc versus Everstream or Interos?

Use Resilinc when the risk graph is built from supplier-attested, self-reported sub-tier and BCP data. Choose Everstream for AI-inferred sub-tier mapping and broad event monitoring, or Interos for interconnected-risk graph modeling across a relationship network.

Can I act on a Resilinc EventWatch alert immediately?

No. An EventWatch alert is an early correlated signal, not a confirmed impact on your network. Corroborate the event and validate affected sites before halting shipments, invoking force majeure, or making any irreversible move.

Why is pushing a Resilinc risk flag into SAP or an ERP dangerous?

The push is a committing write that can trigger automatic supplier blocks, PO cancellations, or re-sourcing in the target system. Check the target's automation posture first; if it auto-acts on the flag or you cannot confirm, treat the push as destructive and hard-gate it.

What are the limitations of supplier-attested data in Resilinc?

Attested data is a self-report, not an audit: suppliers may omit sub-tiers, leave profiles stale, or claim untested recovery times. Mapping completeness is a response rate, not a census, so absence of a sub-tier link is not proof of no exposure.