{"id":42867,"plugin_id":"plugin_asdk_app_699e3e4e050881919b373090d3059dc5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:07:35.505Z","digest":"843608ed9fe7eb8504a7229015f3d53597af2f90dfc32d7aaea30be39ad89026","against":null,"payload":{"description":"Create, evaluate, review, improve, publish, backfill, and govern BuildBetter Smart Tags using durable revisions, real bounded corpora, exact credit receipts, and approval gates. Use when the user asks to build or change a Smart Tag, test classification instructions, review predictions, publish a tag, run historical tagging, or manage tag access and lifecycle.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":251}],"name":"buildbetter-smart-tags","skill_md_contents":"---\nname: buildbetter-smart-tags\ndescription: Create, evaluate, review, improve, publish, backfill, and govern BuildBetter Smart Tags using durable revisions, real bounded corpora, exact credit receipts, and approval gates. Use when the user asks to build or change a Smart Tag, test classification instructions, review predictions, publish a tag, run historical tagging, or manage tag access and lifecycle.\n---\n\n# BuildBetter Smart Tags\n\nFollow [buildbetter-start’s interaction guidance](../buildbetter-start/SKILL.md#interaction): complete supported work through chat; use optional UI only when it reduces effort or clarifies a decision.\n\n## Safety Contract\n\nSearch organization skills with list-skills and get-skill first. Always discover existing groups and members before creating anything. A bounded request to draft and test a Smart Tag authorizes dormant draft edits, the agreed evaluation, review, and disposable draft cleanup. Publishing, historical backfills, access changes, lifecycle changes, group creation, and deletion of non-disposable resources each require exact approval.\n\nIf a named tool is missing from the registered MCP inventory, stop that path. Never emulate Smart Tag mutations through GraphQL.\n\n## Workflow\n\n1. Call list-tag-groups and list-tag-group-tags. Show candidate groups and exact public IDs. Reuse an existing group unless the user explicitly requests a new one.\n2. Restate target object, category breadth, inclusion and exclusion rules, ambiguity handling, evidence sources, and whether multiple or skipped tags are allowed.\n3. Use get-smart-tag-workflow for an existing member. Create-smart-tag-draft for a dormant first version or create-smart-tag-revision for a candidate based on a live tag.\n4. Use suggest-smart-tag-prefilter when a bounded unfiltered sample would be irrelevant. Review accepted and rejected terms; pass accepted keywords directly to run-smart-tag-evaluation rather than adding a redundant draft mutation.\n5. Queue run-smart-tag-evaluation with a client-generated UUID idempotencyKey. Reuse the exact key only after an unknown outcome. Read back the bounded corpus and metered credit scope.\n6. When a jobId and get-job are available, read the standard job receipt and wait pollAfterSeconds between checks; otherwise use get-smart-tag-operation. Report actual state, evaluated objects, exact credits, and errors in chat. When advertised and helpful, show-job-progress provides an optional status snapshot without requiring a click. During discovering_candidates, the final denominator is unknown; do not call a growing scan stuck at zero percent.\n7. Review every prediction needed for a trustworthy corpus with review-smart-tag-evaluation. Explain disagreements. Use improve-smart-tag only with a caller-approved maximum credit budget, then poll its operation.\n8. Publish only after the revision is reviewed and the user approves the exact member, revision, readiness exception if any, and backfill choice.\n9. For a backfill, run the matching preview immediately before approval. Present source-scope, prefilter-matched, eligible counts, and maximum credits. Start or publish with the unchanged approved planning receipt and a new idempotency key.\n10. Monitor get-smart-tag-backfill. Cancellation, resume, lifecycle, access, archive, and deletion are separate decisions.\n\n## State Discipline\n\nUse exact states: dormant draft, candidate revision, evaluation queued or running or completed, reviewed, ready, published, backfill previewed, backfill approved, backfill running, and backfill completed. A local reasoning sample is not a BuildBetter evaluation.\n\n## Output\n\nReport group and member IDs, revision, instructions, corpus scope, operation and planning IDs, idempotency keys without secrets, review metrics, exact credits, approval state, publish state, backfill progress, links, and remaining blockers.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}