joao-aires/agent-skills-public/saas-readiness
Claude Code and agent skill by joao-aires/agent-skills-public
- community
Checking that the SKILL.md file is still in the repository.
Assess a SaaS launch, customer rollout or capability expansion against
Install
npx vskill@latest install joao-aires/agent-skills-public/saas-readinessSKILL.md
The same SKILL.md was published earlier as joao-aires/agent-skills-public/saas-readiness.
Assess readiness for the intended customers
Establish the proposed release/customer cohort, promises, supported journeys, environments and requested decision. Reuse accepted requirements, risk decisions and verification records. A personal pilot, self-service subscription and enterprise deployment have different needs; assess the actual commitment rather than a universal maturity score. Read the source review for illustrative starters and their evidence limits.
Trace commitments to evidence
Turn the proposed customer commitment into journeys that must work for that cohort. Follow each consequential promise through the implementation, the checks performed, and the person or procedure responsible when it fails. This exposes the difference between a feature being present and a customer being able to depend on it.
Assess the evidence at the same scope as the promise. A successful test for one tenant does not establish isolation from another; a recovery procedure does not establish that restoration has been exercised. Identify the missing observation instead of replacing it with a broader confidence statement.
- Include applicable onboarding, tenant/access isolation, commercial state, useful dashboard/admin behavior, recovery, support and offboarding.
- Identify whether evidence is inspected configuration, a passing component check, a persisted integration journey, a production observation or a proposed procedure.
- Avoid converting an absent specialist or an unexecuted check into a pass.
Read capability evidence at cohort scope
Select the areas the proposed commitment actually depends on. For each selected area, ask for the journey and its failure path, not the configuration alone.
| Area | Evidence to seek | Not sufficient | |
|---|---|---|---|
| Supporting services: analytics, email, observability, hosting/edge, marketing and social automation, search, queues, notifications, support | Requirement and chosen shape; an exercised delivery, failure and retry; tenant-scoped data; cost attribution; export and exit | A provider account, dashboard, status page or happy-path test | |
| Billing and entitlements | Provider, local entitlement and usage reconciled; duplicate and out-of-order events; trial, upgrade, dunning, cancellation and refund behavior; enforcement at the action boundary | A successful checkout redirect or a plan label in the interface | |
| Organization and identity | Membership, invitation, role, ownership transfer, SSO/SCIM where promised, machine credentials, support access and revocation window | A role matrix document or a configured IdP connection | |
| Multi-tenancy | Cross-tenant denial across API, search, export and jobs; per-tenant recovery granularity; migration and residency behavior | One tenant's successful journey or an assumption that a shared database is isolated | |
| Compliance evidence | Subprocessors, DPAs, residency, export/deletion, audit records, and Type I/II scope and exceptions where the cohort asks | A policy, trust page, provider attestation or certification claim |
These areas illustrate capability evidence; they are not a universal enterprise checklist. A personal pilot may need only the integration failure path and a deletion procedure, while an enterprise rollout may need SSO, per-tenant recovery and Type II evidence. Scale the request to the cohort and record what was not assessed.
Assess provider dependencies, abuse/quotas, privacy/licensing obligations, artifact/configuration identity, migration/cutover and rollback/forward recovery where they affect the cohort. Seek matching specialists when available; use project evidence and primary sources otherwise. Do not create new customer promises merely because a reference project includes a feature.
Make gaps actionable
Classify each gap before choosing the next action:
| Gap | Distinction to preserve | |
|---|---|---|
| Defect | Behavior falls short of accepted constraints. | |
| Unresolved consequential decision | The authorized owner still needs to settle a choice; proposed risk acceptance remains proposed. | |
| Missing execution or access | The relevant outcome remains unverified. |
For each material gap, explain the affected promise, evidence, consequence and smallest useful next action. Prioritize by impact and likelihood, exposure and recovery, rather than number of checked boxes.
Give one scoped verdict:
- Supported for the stated cohort.
- Supported with explicitly accepted limits.
- Not yet supported by evidence.
State blockers and uncertainty; readiness is not certification or permission to deploy. Carry material learning into existing product/design/operating records without a new tracker or document ceremony. Execute fixes only within the requested scope.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugins/saas-development/skills/saas-readiness/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/joao-aires/agent-skills-public/saas-readiness)