Skip to content
skillsafebeta
← Report library
Purpose / Other

Shipping And Launch Skill Security Audit

What the author says it does (original text)

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Independent security check

Security risks found

Files checked
1
Risks found
4
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.Risks found: 1
Medium risk

Error-reporting examples may disclose user identifiers and request URLs to a monitoring service

Source references: 2
What we found

The client example reports a user ID and page path; the server example reports a user ID and `req.url`. Request URLs can contain tokens, email addresses, search terms, or other personal data in query parameters. No redaction, query filtering, or authorization requirement is stated.

Why this matters

If adopted directly, the error-tracking provider, its personnel, or anyone with monitoring access could receive identifiers and sensitive URL content, creating privacy, compliance, or credential-exposure risk.

The examples explicitly pass page paths and user IDs to an error-reporting function, and the server passes the raw `req.url`. If `reportError` is connected to a third-party service, or URLs contain query parameters, identifiers, tokens, or user input could reach an external monitoring account. The nearby guidance does not require query removal, redaction, or collection limits. Users can ask who receives the data, how long it is retained, and require URL filtering and minimized user identifiers by default.

SKILL.md:193In the instructionsOpen original file
class ErrorBoundary extends React.Component {  componentDidCatch(error: Error, info: React.ErrorInfo) {    // Report to error tracking service    reportError(error, {      componentStack: info.componentStack,      userId: getCurrentUser()?.id,      page: window.location.pathname,    });  }
Show 1 other places
SKILL.md:210In the instructionsOpen original file
// Server-side error reportingapp.use((err: Error, req: Request, res: Response, next: NextFunction) => {  reportError(err, {    method: req.method,    url: req.url,    userId: req.user?.id,  });
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.Risks found: 1
Medium risk

The rollback template can create and push a revert to the wrong remote branch

Source references: 1
What we found

The template presents `git revert <commit> && git push` as deploying a previous version. It actually creates a reversing commit on the current branch and pushes with the current Git credentials, without confirming the repository, branch, commit scope, protection rules, or approval. It also does not ensure the running service was rolled back.

Why this matters

Running it on the wrong branch or commit could undo unrelated code and alter a shared remote repository. The team may also believe production recovered even if the deployment system never used that commit.

The rollback template presents `git revert <commit> && git push` as an executable step. If run directly on the wrong current branch, it creates a reversing commit and pushes with available credentials, affecting the remote repository; the template does not require confirming the repository, branch, target commit, or approval first. Its separate health verification also shows that the Git action alone does not prove production was rolled back. Users can prohibit automatic pushes and require explicit approval after showing the repository, branch, commit, and deployment mapping.

SKILL.md:263In the instructionsOpen original file
### Rollback Steps1. Disable feature flag (if applicable)   OR1. Deploy previous version: `git revert <commit> && git push`2. Verify rollback: health check, error monitoring3. Communicate: notify team of rollback
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.Risks found: 1
Low risk

The install command does not pin a dependency version

Source references: 2
What we found

The installation command does not specify dependency versions. The same command may download different code later, so what you install can differ from what was checked.

Why this matters

A later install may download different code even though the command and this report have not changed.

What this evidence establishes

This is an example in a rollback-plan template, not an explicit installation step. `npx` normally prefers a project-local dependency and may download a package only under conditions such as the dependency being absent. The source does not show whether Prisma is pinned by a lockfile, so unpinned installation is not established. A user can ask the author to require a locked local CLI and a rollback command verified for the project's actual migration tool.

This assessment concerns the code and conditions shown, not proof that harm has occurred.
SKILL.md:271In the instructionsOpen original file
### Database Considerations- Migration [X] has a rollback: `npx prisma migrate rollback`- Data inserted by new feature: [preserved / cleaned up]
Show 1 other places
SKILL.md:270In the instructionsOpen original file
### Database Considerations- Migration [X] has a rollback: `npx prisma migrate rollback`- Data inserted by new feature: [preserved / cleaned up]
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.Risks found: 1
Medium risk

Generic thresholds may be mistaken for release authority without business-specific approval

Source references: 3
What we found

The playbook says to advance a canary only when all thresholds pass and supplies fixed limits for errors, latency, client failures, and business metrics. It does not require calibration for service risk, sample size, statistical confidence, or irreversible business consequences.

Why this matters

If copied unchanged, low-volume services may advance on insufficient evidence, while high-value flows could continue causing revenue, conversion, or user losses that remain inside the generic limits.

The document says to expand the canary only when all thresholds pass and defines fixed percentages for advancing, holding, or rolling back. Although this is guidance rather than automated code, applying it directly could ignore service risk, sample size, and irreversible business effects, leading to premature expansion or rollback. Users can ask that the numbers be labeled as examples and require service-owner approval calibrated to the service's SLOs, traffic, and business impact.

SKILL.md:127In the instructionsOpen original file
4. CANARY rollout (flag ON for 5% of users)   └── Monitor error rates, latency, user behavior   └── Compare metrics: canary vs. baseline   └── 24-48 hour monitoring window   └── Advance only if all thresholds pass (see table below)
Show 2 other places
SKILL.md:144In the instructionsOpen original file
Use these thresholds to decide whether to advance, hold, or roll back at each stage:| Metric | Advance (green) | Hold and investigate (yellow) | Roll back (red) ||--------|-----------------|-------------------------------|-----------------|| Error rate | Within 10% of baseline | 10-100% above baseline | >2x baseline || P95 latency | Within 20% of baseline | 20-50% above baseline | >50% above baseline || Client JS errors | No new error types | New errors at <0.1% of sessions | New errors at >0.1% of sessions || Business metrics | Neutral or positive | Decline <5% (may be noise) | Decline >5% |
SKILL.md:142In the instructionsOpen original file
### Rollout Decision ThresholdsUse these thresholds to decide whether to advance, hold, or roll back at each stage:| Metric | Advance (green) | Hold and investigate (yellow) | Roll back (red) ||--------|-----------------|-------------------------------|-----------------|| Error rate | Within 10% of baseline | 10-100% above baseline | >2x baseline || P95 latency | Within 20% of baseline | 20-50% above baseline | >50% above baseline || Client JS errors | No new error types | New errors at <0.1% of sessions | New errors at >0.1% of sessions || Business metrics | Neutral or positive | Decline <5% (may be noise) | Decline >5% |

Inside this skill

8 instruction sections

This Skill is a production-release playbook covering tests, security, infrastructure, monitoring, and rollback readiness. It provides checklists and examples, with no bundled automation scripts.

View source
SKILL.md:10In the instructionsOpen original file
Ship with confidence. The goal is not just to deploy — it's to deploy safely, with monitoring in place, a rollback plan ready, and a clear understanding of what success looks like. Every launch should be reversible, observable, and incremental.
SKILL.md:311In the instructionsOpen original file
Before deploying:- [ ] Pre-launch checklist completed (all sections green)- [ ] Feature flag configured (if applicable)- [ ] Rollback plan documented- [ ] Monitoring dashboards set up- [ ] Team notified of deployment

It recommends staging verification, production deployment with the feature disabled, then progressive exposure from internal users through a 5% canary and larger cohorts while monitoring each stage.

View source
SKILL.md:115In the instructionsOpen original file
```1. DEPLOY to staging   └── Full test suite in staging environment   └── Manual smoke test of critical flows2. DEPLOY to production (feature flag OFF)   └── Verify deployment succeeded (health check)   └── Check error monitoring (no new errors)3. ENABLE for team (flag ON for internal users)   └── Team uses the feature in production   └── 24-hour monitoring window
SKILL.md:127In the instructionsOpen original file
4. CANARY rollout (flag ON for 5% of users)   └── Monitor error rates, latency, user behavior   └── Compare metrics: canary vs. baseline   └── 24-48 hour monitoring window   └── Advance only if all thresholds pass (see table below)5. GRADUAL increase (25% -> 50% -> 100%)   └── Same monitoring at each step   └── Ability to roll back to previous percentage at any point6. FULL rollout (flag ON for all users)   └── Monitor for 1 week   └── Clean up feature flag```

The TypeScript and shell commands appear inside code blocks or a rollback-plan template. They are examples for an adopter to integrate or run, not code executed by this file itself.

View source
SKILL.md:190In the instructionsOpen original file
```typescript// Set up error boundary with reportingclass ErrorBoundary extends React.Component {  componentDidCatch(error: Error, info: React.ErrorInfo) {    // Report to error tracking service    reportError(error, {      componentStack: info.componentStack,
SKILL.md:255In the instructionsOpen original file
```markdown## Rollback Plan for [Feature/Release]### Trigger Conditions- Error rate > 2x baseline- P95 latency > [X]ms- User reports of [specific issue]### Rollback Steps1. Disable feature flag (if applicable)   OR1. Deploy previous version: `git revert <commit> && git push`2. Verify rollback: health check, error monitoring
Start here · InstructionsSKILL.md
shipping-and-launch
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source. 4 more sections are available in the original file.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions

Operations mentioned in code and instructions

Install extra software packages
SKILL.md:271In the instructionsOpen original file
### Database Considerations- Migration [X] has a rollback: `npx prisma migrate rollback`- Data inserted by new feature: [preserved / cleaned up]
Lines read
331
File checksum (to compare versions)
b22708533783e2e8e9ecb283c133e11c826acad81e4a0aa6651ee18eaf4427db