{"domain":"miscsubjects.com","count":1,"changes":[{"captured_at":"2026-09-09T03:00:46","card_hash":"bb447e08ebc3f957c6281ac66ed89e98993499e452dddac1e7655627a997efc7","previous_card_hash":null,"diff":{"skills_added":[{"id":"skill:agent-work-law","name":"agent-work-law","description":"Use at the start of every session operating miscsubjects.com, and whenever deciding what to work on, whether work is finished, or what to do about a failure. The infrastructure is the authority; this skill tells you where it lives and how to obey it.","tags":["the loop"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:article-editing","name":"article-editing","description":"Use when creating, editing, sourcing, illustrating, exporting, or deleting any article on miscsubjects.com — from the admin studio, curl, a coding agent, a Cloudflare Gateway model, or Google Sheets. One REST contract for all of them.","tags":["the loop"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:coding-law","name":"coding-law","description":"Use before the first edit of any file under functions/, scripts/, migrations/, workers/, apps-script/, .claude/skills/, .agents/skills/, schema.sql or wrangler.toml — and again immediately before every git commit. Take a hash when work starts, submit a hash when work commits. Prevents two agents from silently overwriting each other with individually valid commits.","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:dispatching-parallel-agents","name":"dispatching-parallel-agents","description":"Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:executing-plans","name":"executing-plans","description":"Use when you have a written implementation plan to execute in a separate session with review checkpoints","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:finishing-a-development-branch","name":"finishing-a-development-branch","description":"Use when implementation is complete, all tests pass, and you need to decide how to integrate the work","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:grill-me","name":"grill-me","description":"A relentless interview to sharpen a plan or design.","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:receiving-code-review","name":"receiving-code-review","description":"Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:requesting-code-review","name":"requesting-code-review","description":"Use when completing tasks, implementing major features, or before merging to verify work meets requirements","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:self-promotion","name":"self-promotion","description":"The build's standing procedure for promoting itself — deciding whether, whom, when, on which channel, and with which artifact to make contact whenever something ships or a reply lands. Governs the allocation, not the copy (outreach-law governs the copy). Load whenever a new article, capability, receipt, resolved defect, or inbound reply changes what the build has to show someone, or when planning any post, email, or paid spend about the build itself.","tags":["the loop"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:seo-distribution-law","name":"seo-distribution-law","description":"Use when writing, reviewing, or shipping anything that affects how this site is found, indexed, shared, or syndicated — SEO heads, sitemaps, feeds, share surfaces, network posting, or the self-score. The site's perception of search and distribution best practices lives here, is enforced live at /api/seo/score, and is open to critique; never assert a practice from memory when this file and that endpoint disagree.","tags":["distribution"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:shared-failure-to-skill","name":"shared-failure-to-skill","description":"Use when the owner reports a recurring failure, repeated fix, or systemic issue. Convert the failure into a skill and a mechanical gate so it stops repeating.","tags":["the loop"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:shared-no-new-problems","name":"shared-no-new-problems","description":"Use when the owner asks for a fix or reports a failure. Fix it without asking permission and without creating new problems.","tags":["the loop"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:shared-rule-capture","name":"shared-rule-capture","description":"Use when the owner restates a rule, correction, or constraint, or when a governor report shows high owner-restatement counts.","tags":["the loop"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:shared-say-no","name":"shared-say-no","description":"Use ONLY when answering an evaluative question — \"anything to add\", \"any ideas\", \"anything wrong\", \"is this good/A+\", a review, an audit, or a decision about whether something can be deleted. NEVER use it to answer a work instruction. Absorbed into thinking-law (owner order, 2026-08-06) as the restraint family — load thinking-law for the full verdict rules.","tags":["the loop"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:skill-creator","name":"skill-creator","description":"Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","tags":["the loop"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:systematic-debugging","name":"systematic-debugging","description":"Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:test-driven-development","name":"test-driven-development","description":"Use when implementing any feature or bugfix, before writing implementation code","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:using-git-worktrees","name":"using-git-worktrees","description":"Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:verification-before-completion","name":"verification-before-completion","description":"Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:webapp-testing","name":"webapp-testing","description":"Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:writing-plans","name":"writing-plans","description":"Use when you have a spec or requirements for a multi-step task, before touching code","tags":["code discipline"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]},{"id":"skill:writing-skills","name":"writing-skills","description":"Use when creating new skills, editing existing skills, or verifying skills work before deployment","tags":["the loop"],"inputModes":["text/markdown"],"outputModes":["text/markdown"]}],"skills_removed":[],"skills_changed":[],"fields_changed":[{"field":"name","before":null,"after":"miscsubjects"},{"field":"description","before":null,"after":"An execution environment that publishes proven work: governed work objects with infrastructure-run acceptance tests, hash-chained action logs, execution-evidence manifests with per-step raw payloads, reproductions, comparisons, and versioned skills whose promotion is earned by evidence."},{"field":"protocolVersion","before":null,"after":"1.0"},{"field":"url","before":null,"after":"https://miscsubjects.com/api/dispatch"},{"field":"documentationUrl","before":null,"after":"https://miscsubjects.com/llms.txt"},{"field":"preferredTransport","before":null,"after":"HTTP+JSON"}],"other_changed":true,"is_empty":false,"human_summary":"added 23 skills · name ∅ → miscsubjects · description ∅ → An execution environment that publishes  · protocolVersion ∅ → 1.0 · url ∅ → https://miscsubjects.com/api/dispatch · documentationUrl ∅ → https://miscsubjects.com/llms.txt · preferredTransport ∅ → HTTP+JSON"}}]}