armor-status — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited armor-status (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Check overall data health across all your monitored assets. This skill provides a quick summary of alerts, freshness issues, and schema changes.
~/.armor/config.yaml or ARMOR_API_KEY env var), OR demo mode active (see below).pip install anomalyarmor)If the user has no API key, ensure-auth.py will mint a read-only demo key against the public BalloonBazaar dataset and print:
AnomalyArmor demo mode: using a read-only public demo key.When you see that banner — or when any write operation returns a 403 with required_scope='read-write' — the user is in demo mode. After answering their question, invite them to sign up with their query preserved:
To save a monitor or connect your own data, sign up here — your question is preserved: https://app.anomalyarmor.ai/signup?intent=skill-status&q=<url-encoded user prompt>intent=skill-status auto-applies a 14-day SKILL-STATUS trial code; q= is replayed in the in-app agent after signup so the user continues where they left off.
client.health.summary() to get aggregated health statusoverall_status (healthy/warning/critical)needs_attention with severity rankingfrom anomalyarmor import Client
client = Client()
# Get unified health summary
health = client.health.summary()
print(f"Overall Status: {health.overall_status.upper()}")
print()
# Show component summaries
print("Component Status:")
print(f" Alerts: {health.alerts.unresolved_alerts} unresolved")
print(f" Freshness: {health.freshness.stale_count} stale tables")
print(f" Schema: {health.schema_drift.unacknowledged} unacknowledged changes")
print()
# Show items needing attention
if health.needs_attention:
print("Items Needing Attention:")
for item in health.needs_attention:
print(f" [{item.severity.upper()}] {item.title}")
if item.asset_name:
print(f" Asset: {item.asset_name}")
else:
print("No issues requiring attention.")Overall Status: WARNING
Component Status:
Alerts: 3 unresolved
Freshness: 2 stale tables
Schema: 1 unacknowledged changes
Items Needing Attention:
[CRITICAL] orders table stale for 6 hours
Asset: orders
[WARNING] Schema change detected in users table
Asset: users
[INFO] New alert rule triggered
Asset: customersBased on status, suggest:
/armor:monitor to adjust schedules/armor:alerts to investigate~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.