{"id":83777,"plugin_id":"plugin_asdk_app_6adfeb1c0ad4819186c00c8e34352db0","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-06T00:16:27.222Z","digest":"50413152fabf4e5f46fc07457e28700b7588e500fc900f451cac058836cfae22","against":null,"payload":{"description":"Add the PathToShip readiness badge to a README or site after a scan clears the ship bar. Use when get_score or verify_fix returns verdict \"ready\", or when the user asks to show their readiness score.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":708},{"relative_path":"assets/icon.png","size_in_bytes":7687}],"name":"pathtoship-badge","skill_md_contents":"---\nname: pathtoship-badge\ndescription: Add the PathToShip readiness badge to a README or site after a scan clears the ship bar. Use when get_score or verify_fix returns verdict \"ready\", or when the user asks to show their readiness score.\n---\n\n# Readiness badge\n\nWhen an app clears the ship bar, the score is worth showing — to users, clients, and the next developer. The badge is a live SVG that always reflects the scan it points to and links to the public report.\n\n## When\n\n- `get_score` or `verify_fix` returns `verdict: \"ready\"` — offer once, do not nag.\n- The user asks to display or share their score on the README or site.\n\n## Procedure\n\n1. Confirm with `get_score` that the verdict is `ready` and note `scan_id` and `permalink`. If it is `conditional` or `not_ready`, say so and do not add a badge — a badge under the bar helps no one.\n2. Offer the badge and, if the user agrees, add it:\n   - README (Markdown), replacing the placeholders:\n\n     ```markdown\n     [![PathToShip Score: SCORE/100](https://pathtoship.com/api/badge/SCAN_ID)](PERMALINK)\n     ```\n\n   - Site (an image linked to the report): the same badge URL as the image source, the permalink as the link target, and \"PathToShip Score: SCORE/100\" as the alt text.\n   - Variants via `?variant=gauge` or `?variant=minimal` on the badge URL; the default is fine for a README.\n3. Show the user the change. Place it near the top of the README (under the title) or in the site footer — where a visitor would look for trust signals. Suggest the commit message `docs: add PathToShip readiness badge`; the user or their builder commits it.\n4. After later changes, the badge keeps pointing at _that_ scan. When the user runs a new scan that is also `ready`, offer to update the `scan_id` so the badge reflects the current code. If a later scan drops below the bar, tell the user the badge is stale and offer to remove it rather than leave a misleading one.\n\n## What the badge says\n\nThe badge shows the PathToShip score of one automated scan of one commit. It is not a security certification, an audit, or a compliance attestation, and you should not describe it as one.\n\n## Rules\n\n- Never add a badge for a scan that is not `ready`, and never edit the score text by hand — the SVG renders the real number.\n- One badge per app; do not stack variants.\n- Set `trigger: \"skill\"` on tool calls this skill initiates.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}