Content
75%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.
A well-structured, information-dense skill body: concrete tooling, real file map, dependency-ordered integration strategy, and a pre-submit checklist. All dimensions sit just below the top anchors due to repeated doc-fetch admonitions, an outline-only code example, no explicit retry loop for batch sync, and an API table that could move to the reference file.
Suggestions
Move the API Capabilities Quick Reference table (with the known-gaps list) into `references/nicolify-integration.md` or a dedicated API reference file, keeping only the known-gaps summary inline.
Replace the 'Example: Adding Subscriber Sync' outline with one worked, copy-paste-ready snippet — e.g., an actual `find_subscriber_by_email` connector method using httpx.AsyncClient with the bearer header.
Add an explicit validation/feedback step to the sync workflow (e.g., verify upsert counts, retry with backoff on 429, log and continue on per-subscriber failure) since subscriber sync is a batch operation.
Consolidate the fetch-fresh-docs emphasis into Step 0 alone and drop the repeats in the intro, quick-reference note, and checklist to save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with actionable tables (rate limits, file map, extension steps) and assumes Claude's competence, never explaining what ManyChat or webhooks are. It stops short of the top anchor because the fetch-fresh-docs admonition is repeated in the intro, Step 0, the quick-reference note, and the checklist — repetition that could be trimmed. | 4 / 5 |
Actionability | Guidance is concrete and executable: exact MCP tool calls ('mcp__plugin_context7_context7__resolve-library-id'), endpoint names ('/fb/sending/sendFlow', 'GET /fb/subscriber/findByCustomField'), file paths, and framework specifics (httpx.AsyncClient, Pydantic v2, Depends(get_current_user), user.tenant_id). It misses the top anchor because the 'Example: Adding Subscriber Sync' is an outline of steps rather than copy-paste-ready code or a worked payload. | 4 / 5 |
Workflow Clarity | Sequences are clear and ordered by dependency (Step 0 doc fetch with cross-reference checkpoint, backend steps 1–5, strategy items 1–6), and the 'Checklist Before Submitting ManyChat Code' plus 429 backoff guidance provide most checkpoints. It does not reach the top anchor because the batch subscriber-sync workflow lacks an explicit validate-failure-then-retry feedback loop. | 4 / 5 |
Progressive Disclosure | The SKILL.md acts as an overview with a clearly signaled, one-level-deep reference ('Read `references/nicolify-integration.md` for the full file map. Summary:') to a real file, with a useful inline summary table. It falls short of the top anchor because the ~30-line API Capabilities Quick Reference table is inline detail that arguably belongs in the reference file. | 4 / 5 |
Total | 16 / 20 Passed |