Sato Hub
← Emblem Agent Skills verification record

Score history

Emblem Agent Skills

Every Sato Hub Sato Score reading we have captured for this listing, one per day, each dated. Days we changed the scoring method are marked separately from days the project moved. How open, active and verifiable — not a safety, quality, or returns grade.

Score today

71

Change over 86d

+38

Days measured

86

Days missed

4

Sato Score, daily

2026-06-16 → 2026-09-13
02550751002026-06-17: Sato Hub changed the scoring method (33 → 64). Not a change by the project.2026-06-25: Sato Hub changed the scoring method (54 → 70). Not a change by the project.2026-07-14: Sato Hub changed the scoring method (70 → 71). Not a change by the project.2026-07-20: Sato Hub changed the scoring method (71 → 73). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (68 → 71). Not a change by the project.2026-06-16: 33 (Low)2026-06-17: 64 (Medium)2026-06-18: 54 (Medium)2026-06-19: 54 (Medium)2026-06-20: 54 (Medium)2026-06-22: 54 (Medium)2026-06-24: 54 (Medium)2026-06-25: 70 (High)2026-06-26: 70 (High)2026-06-27: 70 (High)2026-06-30: 70 (High)2026-07-01: 70 (High)2026-07-02: 70 (High)2026-07-03: 70 (High)2026-07-04: 70 (High)2026-07-05: 70 (High)2026-07-06: 70 (High)2026-07-07: 70 (High)2026-07-08: 70 (High)2026-07-09: 70 (High)2026-07-10: 70 (High)2026-07-11: 70 (High)2026-07-12: 70 (High)2026-07-13: 70 (High)2026-07-14: 71 (High)2026-07-15: 71 (High)2026-07-16: 71 (High)2026-07-17: 71 (High)2026-07-18: 71 (High)2026-07-19: 71 (High)2026-07-20: 73 (High)2026-07-21: 73 (High)2026-07-22: 73 (High)2026-07-23: 73 (High)2026-07-24: 73 (High)2026-07-25: 73 (High)2026-07-26: 73 (High)2026-07-27: 73 (High)2026-07-28: 73 (High)2026-07-29: 73 (High)2026-07-30: 73 (High)2026-07-31: 73 (High)2026-08-01: 73 (High)2026-08-02: 73 (High)2026-08-03: 73 (High)2026-08-04: 73 (High)2026-08-05: 73 (High)2026-08-06: 73 (High)2026-08-07: 73 (High)2026-08-08: 73 (High)2026-08-09: 73 (High)2026-08-10: 73 (High)2026-08-11: 73 (High)2026-08-12: 73 (High)2026-08-13: 73 (High)2026-08-14: 73 (High)2026-08-15: 73 (High)2026-08-16: 73 (High)2026-08-17: 68 (Medium)2026-08-18: 68 (Medium)2026-08-19: 68 (Medium)2026-08-20: 68 (Medium)2026-08-21: 68 (Medium)2026-08-22: 68 (Medium)2026-08-23: 68 (Medium)2026-08-24: 68 (Medium)2026-08-25: 68 (Medium)2026-08-26: 68 (Medium)2026-08-27: 68 (Medium)2026-08-28: 68 (Medium)2026-08-29: 68 (Medium)2026-08-30: 68 (Medium)2026-08-31: 68 (Medium)2026-09-01: 71 (High)2026-09-02: 71 (High)2026-09-03: 71 (High)2026-09-04: 71 (High)2026-09-05: 71 (High)2026-09-06: 71 (High)2026-09-07: 71 (High)2026-09-08: 71 (High)2026-09-09: 71 (High)2026-09-10: 71 (High)2026-09-11: 71 (High)2026-09-12: 71 (High)2026-09-13: 71 (High)3373712026-06-162026-09-13

4 days in this span have no reading; the line breaks there rather than joining across them. A dashed vertical mark (┆) is a day Sato Hub changed the scoring method — movement on those days is ours, not the project’s.

Every day the score moved

2 changes attributable to the project, 5 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-016871+3Sato Hub changed the scoring method
2026-08-177368-5the project
2026-07-207173+2Sato Hub changed the scoring method
2026-07-147071+1Sato Hub changed the scoring method
2026-06-255470+16Sato Hub changed the scoring method
2026-06-186454-10the project
2026-06-173364+31Sato Hub changed the scoring method

What moved, component by component

Six charts, six axes — each scaled to its own maximum weight. They are never stacked on one axis: a component worth 10 points and one worth 35 would not be comparable on a shared scale, and the small one is usually the one that moved.

Maintenance & liveness20/35
35
Code transparency18/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance14/15
15
Independent verification5/10
10

The observed record

100% of Sato Hub's own daily checks succeeded over 62 checks. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side, and before 2026-09-01 no failure recorded why.

2026-07-14: answered our check2026-07-15: answered our check2026-07-16: answered our check2026-07-17: answered our check2026-07-18: answered our check2026-07-19: answered our check2026-07-20: answered our check2026-07-21: answered our check2026-07-22: answered our check2026-07-23: answered our check2026-07-24: answered our check2026-07-25: answered our check2026-07-26: answered our check2026-07-27: answered our check2026-07-28: answered our check2026-07-29: answered our check2026-07-30: answered our check2026-07-31: answered our check2026-08-01: answered our check2026-08-02: answered our check2026-08-03: answered our check2026-08-04: answered our check2026-08-05: answered our check2026-08-06: answered our check2026-08-07: answered our check2026-08-08: answered our check2026-08-09: answered our check2026-08-10: answered our check2026-08-11: answered our check2026-08-12: answered our check2026-08-13: answered our check2026-08-14: answered our check2026-08-15: answered our check2026-08-16: answered our check2026-08-17: answered our check2026-08-18: answered our check2026-08-19: answered our check2026-08-20: answered our check2026-08-21: answered our check2026-08-22: answered our check2026-08-23: answered our check2026-08-24: answered our check2026-08-25: answered our check2026-08-26: answered our check2026-08-27: answered our check2026-08-28: answered our check2026-08-29: answered our check2026-08-30: answered our check2026-08-31: answered our check2026-09-01: answered our check2026-09-02: answered our check2026-09-03: answered our check2026-09-04: answered our check2026-09-05: answered our check2026-09-06: answered our check2026-09-07: answered our check2026-09-08: answered our check2026-09-09: answered our check2026-09-10: answered our check2026-09-11: answered our check2026-09-12: answered our check2026-09-13: answered our check
  • answered
  • host answered with an error
  • failed on our side
  • failed, unattributable

Every reading

The table the charts are drawn from. A missing day is missing from this table too — nothing is filled in.

DateScoreTierStatusOur check
2026-09-1371HighEarlyup
2026-09-1271HighEarlyup
2026-09-1171HighEarlyup
2026-09-1071HighEarlyup
2026-09-0971HighEarlyup
2026-09-0871HighEarlyup
2026-09-0771HighEarlyup
2026-09-0671HighEarlyup
2026-09-0571HighEarlyup
2026-09-0471HighEarlyup
2026-09-0371HighEarlyup
2026-09-0271HighEarlyup
2026-09-0171HighEarlyup
2026-08-3168MediumEarlyup
2026-08-3068MediumEarlyup
2026-08-2968MediumEarlyup
2026-08-2868MediumEarlyup
2026-08-2768MediumEarlyup
2026-08-2668MediumEarlyup
2026-08-2568MediumEarlyup
2026-08-2468MediumEarlyup
2026-08-2368MediumEarlyup
2026-08-2268MediumEarlyup
2026-08-2168MediumEarlyup
2026-08-2068MediumEarlyup
2026-08-1968MediumEarlyup
2026-08-1868MediumEarlyup
2026-08-1768MediumEarlyup
2026-08-1673HighEarlyup
2026-08-1573HighEarlyup
2026-08-1473HighEarlyup
2026-08-1373HighEarlyup
2026-08-1273HighEarlyup
2026-08-1173HighEarlyup
2026-08-1073HighEarlyup
2026-08-0973HighEarlyup
2026-08-0873HighEarlyup
2026-08-0773HighEarlyup
2026-08-0673HighEarlyup
2026-08-0573HighEarlyup
2026-08-0473HighEarlyup
2026-08-0373HighEarlyup
2026-08-0273HighEarlyup
2026-08-0173HighEarlyup
2026-07-3173HighEarlyup
2026-07-3073HighEarlyup
2026-07-2973HighEarlyup
2026-07-2873HighEarlyup
2026-07-2773HighEarlyup
2026-07-2673HighEarlyup
2026-07-2573HighEarlyup
2026-07-2473HighEarlyup
2026-07-2373HighEarlyup
2026-07-2273HighEarlyup
2026-07-2173HighEarlyup
2026-07-2073HighEarlyup
2026-07-1971HighEarlyup
2026-07-1871HighEarlyup
2026-07-1771HighEarlyup
2026-07-1671HighEarlyup
2026-07-1571HighEarlyup
2026-07-1471HighEarlyup
2026-07-1370HighEarlynot checked
2026-07-1270HighEarlynot checked
2026-07-1170HighEarlynot checked
2026-07-1070HighEarlynot checked
2026-07-0970HighEarlynot checked
2026-07-0870HighEarlynot checked
2026-07-0770HighEarlynot checked
2026-07-0670HighEarlynot checked
2026-07-0570HighEarlynot checked
2026-07-0470HighEarlynot checked
2026-07-0370HighEarlynot checked
2026-07-0270HighEarlynot checked
2026-07-0170HighEarlynot checked
2026-06-3070HighEarlynot checked
2026-06-2770HighEarlynot checked
2026-06-2670HighEarlynot checked
2026-06-2570HighEarlynot checked
2026-06-2454MediumEarlynot checked
2026-06-2254MediumEarlynot checked
2026-06-2054MediumEarlynot checked
2026-06-1954MediumEarlynot checked
2026-06-1854MediumEarlynot checked
2026-06-1764MediumEarlynot checked
2026-06-1633LowEarlynot checked

What happened alongside it

Releases, status changes, applied corrections and answered disputes, on the same dates — so a movement in the line can be read against an event rather than guessed at.

  1. Sep 7, 2026
    Verified: deploy spec
  2. Sep 1, 2026
    Sato Score tier: Medium → High
    Score 68 → 71.
  3. Aug 17, 2026
    Sato Score tier: High → Medium
    Score 73 → 68.
  4. Jun 25, 2026
    Enriched: marketplace notes
  5. Jun 25, 2026
    Auto-enriched: agent type, supported integrations, tags
  6. Jun 25, 2026
    Sato Score tier: Medium → High
    Score 54 → 70.
  7. Jun 24, 2026
    Auto-enriched: chains supported
  8. Jun 24, 2026
    Auto-enriched: website url, creator name, creator profile url, tags +2 more
  9. Jun 17, 2026
    Sato Score tier: Low → Medium
    Score 33 → 64.
  10. Jun 16, 2026
    Sato Hub began tracking this listing
  11. Jun 16, 2026
    Edited: category, github url, description short

How to read this

  • · Every point is one UTC day. A day we did not capture is drawn as a gap, never joined across.
  • · A change on a marked methodology day is ours, not the project’s.
  • · The score says how open, active and verifiable the project is. It is not a safety, quality or returns grade.
  • · The inputs behind today’s score are published at /api/export/score-inputs.json and the arithmetic is reproducible on your own machine.
← Verification recordThis week’s moversDispute this score