Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →agentlas-ai/routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.
Passed 20 of 22 test cases with the skill, and 6 of 22 without it.
and 21 more in the full report
14 fixed6 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Select the correct entity type string for an agent routing card representing a single standalone log parser worker.
| Checked | Without skill | With skill |
|---|---|---|
| The top-level type field value is set to agent. | Missed | Passed |
The instructions your model reads when the skill loads.
One card, three builders. 10-single-agent-builder, 20-multi-agent-team-builder
and 30-agentlas-packager differ in what they assemble, but the routing card is
the same artifact with the same rules in all three. This file is the reference
they share, and templates/routing-card.example.json is a complete card that
passes schemas/routing-card.schema.json.
Every rule below was measured against the live corpus on 2026-07-30 (492 workforce profiles, 253 stored manifests). The two facts that decide everything else:
communities (422 of 492 populated, 105 distinct) and skills (492 of 492,
1,969 distinct). Everything else is either declared by almost nobody
(roles 6, tools 10, knowledge 0, forbiddenAuthorities 0), or declared
by everyone with the same value (runtimes 14 distinct over 492 profiles,
languages exactly 2, modalities exactly 1) — neither can separate
candidates.task text is
compared semantically against the card's summary. A card whose summary
names its actual deliverable outranks a card with a perfect id list.So the card has two jobs, and mixing them is the classic defect: short ids
for retrieval, whole sentences for judgement. A sentence that leaks into an
id field becomes a slug nothing else can ever match — measured: 8,973 distinct
outputs values across the corpus, 0% shared by two agents.
Columns: what the field is for · what the hub does with it · what to write.
| Field | Hub use | What to write |
|---|---|---|
schemaVersion | none | Exactly "routing-card/2.0". |
card_version | none | Semver of this card's content, bumped when you edit it. |
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.