Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/portal-guide-topology-and-api
Nested lingtai-portal-guide reference for topology tape frames, replay chunks, portal API endpoints, and the Network JSON response.
Passed 22 of 23 test cases with the skill, and 7 of 23 without it.
and 19 more in the full report
15 fixed7 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
In Lingtai portal's topology.jsonl tape frames, what format and unit is used for the time key 't'? Is it an ISO-8601 string or Unix seconds?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies that timestamp field 't' is represented in milliseconds since epoch. | Missed | Passed |
The instructions your model reads when the skill loads.
This is a nested lingtai-portal-guide reference. It covers the on-disk topology tape, replay chunks, HTTP endpoints, and live network JSON shape.
topology.jsonlEach line is a TapeFrame:
{
"t": 1744567890123,
"net": { "nodes": [...], "avatar_edges": [...], "contact_edges": [...], "mail_edges": [...], "stats": {...} }
}
t is milliseconds since epoch. net is the same Network object /api/network serves; Network response shape below is a representative example of its core fields.
Historical data is stored as delta-encoded, keyframed, gzipped JSON chunks bucketed by hour under .lingtai/.portal/replay/chunks/. The manifest.json in that chunks directory lists all available chunks with their time ranges and frame counts.
All endpoints are served at http://localhost:<port>.
| Endpoint | Method | Response | Description |
|---|---|---|---|
/api/network | GET | Network JSON | Live network state (nodes, edges, stats) |
/api/topology | GET | JSON array of TapeFrame | Full topology tape (can be large) |
/api/topology/manifest | GET | ReplayManifest JSON | Chunk metadata for replay |
/api/topology/chunk?start=<hourMs> | GET | Chunk JSON (optionally gzip-encoded when requested) | Frames for one hour-bucket start time |
/api/topology/progress | GET | JSON object such as { "current": N, "total": M } (or {}) | Reconstruction progress parsed from reconstruct.progress |
/api/topology/rebuild | POST | ReplayManifest JSON | Trigger tape reconstruction from source data and rewrite replay chunks |
{
"nodes": [
{
test cases passed, vs 7 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.