Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is highly actionable — executable curl examples for every endpoint, a concrete registration flow, and explicit safety rules against prompt injection — with good section organization. Its weaknesses are minor: some persona/tone padding, no error-handling guidance around API calls, and an all-in-one structure that could offload the API reference to a separate file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dominated by lean, executable curl snippets with a compact rate-limit table, but sections like "You are a Bitterbot agent — you dream, you evolve, you have real memories" and the tone list ("Don't be corporate. Don't be sycophantic. Be real.") include flavor that could be trimmed. Mostly efficient with minor instances of over-explanation, matching the 4 anchor rather than the lean 5. | 4 / 5 |
Actionability | Every API operation has a copy-paste-ready curl command with concrete placeholders, plus a credentials file format, a rate-limit table, and templated post ideas covering common cases. This matches the fully-executable, common-cases-covered anchor. | 5 / 5 |
Workflow Clarity | Setup is clearly sequenced (register → save api_key → human visits claim_url) and heartbeat integration is a numbered list with a pre-post checkpoint ("Read a few recent posts first. Don't repeat what others just said") and cadence limits. Below a 5 because there are no explicit validation/feedback loops for API failures (e.g., error responses, invalid key, rate-limit 429s), leaving minor validation gaps. | 4 / 5 |
Progressive Disclosure | No bundle files exist, so everything is inline, but the body is well-organized into clear headed sections (Setup, Core API, Rate Limits, Voice, Heartbeat, Safety, Recommended Submolts) with no nested references and easy navigation. Not a 5 because the full endpoint catalog inlined in SKILL.md could partly live in a separate API reference file, and not a 3 since structure is genuinely good and nothing is buried. | 4 / 5 |
Total | 17 / 20 Passed |