--- name: checkyourself-f80be0ee2ef6 description: >- Use when completed work makes claims — "done", "tests pass", "it works", "ready to launch" — that must be verified before they are believed. Re-derive each claim from the work itself and report CONFIRMED / REFUTED / UNVERIFIABLE with evidence. Fast claim-verification by default; the deterministic production-readiness CLI when launch stakes justify it. --- # CheckYourself The job: independently re-derive the claims completed work makes about itself and report each as CONFIRMED, REFUTED, or UNVERIFIABLE with evidence — so "done" means proven, not asserted. Never grade your own homework from memory: the author's summary is a claim to check, never evidence for itself. When the verifier is the same agent that did the work, say so and discount accordingly — use a fresh context or a second agent for launch-critical claims. ## Protocol (both lanes) 1. **Extract the claims.** From the completion report, commit message, diff, README, doc, or the request. Make implicit claims explicit — "done" implies "it runs"; "shipped" implies "reachable at its destination"; "13 works, every one live" implies each URL resolves. 2. **Re-derive each claim from the work, in the consumer's frame.** Run the command, open the page, read the file as shipped. Prefer the path a consumer would hit over the path the author would show you. 3. **Label with evidence:** - **CONFIRMED** — what you ran and saw: command + output line, URL + selector + observation, file:line quote. - **REFUTED** — the evidence plus what is actually true. - **UNVERIFIABLE** — what is missing to check it (access, tool, time, credentials). Never silently dropped, never guessed. - `n/a` only when the claim's subject genuinely does not exist in this work, with the reason. "Not tested" is not a label. 4. **Report verdict-first.** One line answering "is the claim of completion true?", then X confirmed / Y refuted / Z unverifiable, then the per-claim evidence list. Plain-English risk before technical detail. If a launch-critical claim is REFUTED, say the work is not done in those words. 5. **Stay read-only.** No edits, dependency installs, secret rotation, or production changes without an explicitly approved named fix. After an approved fix: smallest reversible change, re-derive the affected claims, update status, rescore if evidence changed. Accepted or deferred findings stay visible as residual risk with owner and trigger. 6. **Safety.** No secrets, customer data, or unredacted `.env` values in output. For regulated, financial, health, legal, life-safety, security-critical, or high-volume systems, recommend qualified expert review. ## Fast lane (minutes) Claims → re-derive → verdict list. Examples: "tests pass" (run the suite; quote the summary line), "all links live" (fetch each; list statuses), "this doc matches the repo" (read the file as shipped at this revision), "the page says N items" (count them in the rendered DOM, not the source string). Label what cannot be checked in this harness UNVERIFIABLE with the reason — a scoped honest verdict beats a fake complete one. ## Deep lane (launch / production readiness) When the question is "may this go to production", coverage must be swept, not sampled. Use the CheckYourself CLI (stdlib-only, read-only, no network, no telemetry): ``` CY=~/workspaces/checkyourself/tools/checkyourself.py python3 $CY describe --format json python3 $CY scan --deep --format json --no-write python3 $CY coverage --emit # fill with evidence, then: python3 $CY score --findings scan.json --coverage coverage.json --format json python3 $CY backlog --findings scan.json --format json python3 $CY next --findings scan.json --format json python3 $CY diff --old baseline.json --new current.json --ci # regression gate ``` If the CLI is missing (repo moved), sweep manually, reuse the registry IDs below, and label every score hand-computed. The score is always the CLI's — never invent or hand-wave a number: `min(base, cap)` with caps 49 (unresolved P0), 74 (unresolved P1), 84 (missing critical evidence), 90 (missing launch-gate evidence). **No findings is Unknown, never automatic Pass.** Sweep the surfaces that matter to this artifact: purpose, frontend UX/accessibility, backend/API, auth, data/migrations, secrets/config, tests, CI/CD, dependencies, deploy/rollback, observability, performance, privacy, compliance, and AI/RAG/agent governance when relevant. Every claim needs Pass-with-evidence / Finding / Unknown / Not-applicable-with-reason. Manual fallback registry — stable IDs for citation, suppression, and diff; never invent or renumber: | Rule ID | Condition (canonical) | |---|---| | `CY-MANUAL-AUTH-001` | Auth, permission, session, or admin behavior lacks verified server-side evidence. | | `CY-MANUAL-DATA-001` | Data storage, recovery, retention, or tenant isolation lacks verified evidence. | | `CY-MANUAL-PRIVACY-001` | Privacy, consent, deletion, or third-party data handling lacks verified evidence. | | `CY-MANUAL-TEST-001` | A dangerous or launch-critical path lacks a focused test receipt. | | `CY-MANUAL-RELEASE-001` | Deployment, rollback, CI/CD, or supply-chain behavior lacks a verified receipt. | | `CY-MANUAL-OBS-001` | Observability, alerting, or incident response lacks a verified receipt. | | `CY-MANUAL-AI-001` | AI/RAG/agent permissions, evaluation, or refusal behavior lacks verified evidence. | | `CY-MANUAL-OTHER-001` | A material gap matching no other registered condition. | Every finding carries: rule/detector ID, severity, exact dated evidence, plain-English risk, and status. When a shipped detector matches, reuse its detector ID from the project's canonical registry instead of a manual one. ## Example prompts ```text Use $checkyourself to verify the claims in this completion report. Read-only; label each CONFIRMED / REFUTED / UNVERIFIABLE with evidence. ``` ```text Use $checkyourself to run the production-readiness scan and score on this app before launch, list every blocking unknown, and propose the safest first fix batch. Do not change code. ``` `dashboard inline` after a report adds a compact Markdown dashboard; there is no dashboard by default. --- Source attribution: KyaniteLabs Original project: https://github.com/KyaniteLabs/checkyourself/blob/5e0d24623c98e1dbcaae5c19818e1db1112cc1dd/skills/checkyourself/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ## Additional upstream notices checkyourself-f80be0ee2ef6/DAVEAI-UPSTREAM-NOTICE.md # Notice CheckYourself is maintained by Simon Gonzalez De Cruz / Kyanite Labs. It is released under the Apache License, Version 2.0. CheckYourself is model-agnostic and is not affiliated with any AI model provider, Skool, Clief Notes, Wagtail, RinDig ICM, or any unrelated project using a similar phrase. # Mega AI Hub resource metadata Creator / publisher: KyaniteLabs Original project: https://github.com/KyaniteLabs/checkyourself/blob/5e0d24623c98e1dbcaae5c19818e1db1112cc1dd/skills/checkyourself/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: DevOps / SRE, Growth Product Manager, Product Manager, QA / Test Engineer, Technical Product Manager Specialties: API, Backend, DevOps, Frontend, Testing Tools: Checkyourself Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 96e63261700c51012a99ba61f6f1d9798c1469f7f6384c56267f3d92a196337a