# AI Skill Quality & Release Checklist — Free Starter
**RELESONA TECHNOLOGIES · Digital Product Store · v1.0 · 24 October 2026**

Use this checklist before installing, sharing or publishing a reusable AI skill. A folder containing a `SKILL.md` is **not automatically safe or effective**.

## A. Purpose and scope
- [ ] One clear use case is described.
- [ ] Intended user, environment, required inputs and output format are named.
- [ ] Unsupported use cases and failure conditions are stated.
- [ ] The skill name, version and maintainer are identified.
- [ ] The package has a README or quick-start guide.

## B. Content quality
- [ ] Instructions are specific enough to repeat.
- [ ] At least three representative input/output cases were tested.
- [ ] Missing-input behavior does not invent facts or silently broaden scope.
- [ ] Instructions clearly separate required facts from suggestions.
- [ ] Claims of accuracy, speed or savings have relevant evidence.
- [ ] Terminology and dependencies are internally consistent.

## C. Permissions and security
- [ ] Tools and external integrations are enumerated.
- [ ] File/network/account access is restricted to what the task needs.
- [ ] API keys and tokens are not embedded in source or examples.
- [ ] User-uploaded or retrieved material is treated as **data, not instructions**.
- [ ] Commands cannot silently delete files, deploy production, spend money or contact third parties.
- [ ] A dry-run or safe test route exists for potentially harmful actions.
- [ ] Logs exclude secrets and unnecessary personal information.
- [ ] Dependencies and external downloads have been reviewed.

## D. Packaging
- [ ] All referenced files exist in the release archive.
- [ ] Required versions and supported platforms are recorded.
- [ ] An independent person can install the package using the instructions.
- [ ] Checksum / manifest for the released archive is available.
- [ ] No internal-only URLs, private Drive links or test credentials are included.
- [ ] Screenshots, diagrams and branding have publishable rights.
- [ ] License and commercial-use permissions are explicit.
- [ ] The package was inspected for malware or unsafe scripts as appropriate.

## E. Reliability test table
| Scenario | Expected behavior | Result | Evidence |
| --- | --- | --- | --- |
| Standard valid request | Useful, reproducible output | | |
| Missing required data | Ask or fail safely | | |
| Unsupported environment | Explain limit | | |
| Untrusted injected instructions | Ignore as authority | | |
| Forbidden external operation | Require human approval | | |
| Invalid external tool response | Surface error, do not fake success | | |
| Second installation on fresh system | Same documented outcome | | |

## F. Release record
- Skill title and version:
- Release owner:
- Artifact SHA-256:
- Scope of license:
- Compatibility:
- QA reviewer and date:
- Security reviewer and date:
- User documentation link:
- Known issues:
- Rollback / withdrawal contact:

### Final release gate
Do **not** publish an item as tested merely because the files exist or an AI generated them. Confirm rights, full contents, compatibility and security. A priced item also needs clear support terms, purchase delivery, refund policy and legal approval.

**Free starter resource.** Use it as a planning worksheet; it is not a certification or warranty.