interview-me
78Clarify User Intent Before You Build
Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.
Plan Safer Production Launches
Production releases can fail without clear gates, monitoring, and rollback criteria. This skill creates a structured launch plan for controlled, observable deployment.
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "shipping-and-launch" from https://skillstore.io/skills/addyosmani-shipping-and-launch.md and its manifest at https://skillstore.io/api/skills/addyosmani-shipping-and-launch/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Utilisation de « shipping-and-launch ». Plan the launch of a task-sharing feature behind a feature flag.
Résultat attendu:
Utilisation de « shipping-and-launch ». Create rollback criteria for a database-backed release.
Résultat attendu:
Rollback triggers include data-integrity failures, doubled error rates, major latency regression, or security issues. Verify application and migration recovery separately.
Utilisation de « shipping-and-launch ». Review readiness for a public beta.
Résultat attendu:
All static findings are false positives caused by Markdown formatting, fenced examples, checklist text, or documentation links. The skill provides launch guidance but contains no executable automation, prompt injection, or malicious intent.
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
https://skillstore.io/skills/addyosmani-shipping-and-launch/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-shipping-and-launch?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/addyosmani-shipping-and-launch?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-shipping-and-launch/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/addyosmani-shipping-and-launch.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>addyosmani. (2026). shipping-and-launch security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-shipping-and-launch/audits/1@techreport{addyosmani-addyosmani-shipping-and-launch-2026,
author = {addyosmani},
title = {shipping-and-launch security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/addyosmani-shipping-and-launch/audits/1},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "shipping-and-launch security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-shipping-and-launch/audits/1"
identifiers:
- type: other
value: "skillstore:addyosmani-shipping-and-launch:audit:1"
description: "Skillstore immutable audit report identifier"
Create a release checklist, rollout stages, success metrics, and rollback triggers for a new production feature.
Assess whether quality, infrastructure, monitoring, documentation, and operational controls are ready before approval.
Define canary percentages, observation windows, ownership, communications, and decision thresholds across participating teams.
Create a pre-launch checklist for [feature]. The stack is [stack], and deployment uses [platform]. Highlight missing information.
Plan a staged rollout for [change]. Include feature-flag states, audience percentages, observation windows, owners, and advance or rollback criteria.
Create a rollback plan for [release]. Consider application code, database changes, user data, dependencies, communications, verification, and recovery time.
Evaluate this launch plan against quality, security, performance, accessibility, observability, error-budget, and rollback requirements: [plan]. Return blockers and required actions.
Auteur
addyosmaniLicence
MIT
Révision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
Réf
5d5054f8a23586f9b500fece1cb613a9dffc787b
Récence de maintenance
19/09/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đ SKILL.md
Clarify User Intent Before You Build
Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.
Examiner le code selon cinq axes de qualité
Les modifications de code peuvent dissimuler des problĂšmes de fiabilitĂ©, de sĂ©curitĂ©, dâarchitecture, de lisibilitĂ© et de performances. Cette compĂ©tence applique un processus dâexamen structurĂ© et produit des retours hiĂ©rarchisĂ©s et exploitables.
Plan Work Into Verifiable Tasks
Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.
Document Decisions and Architecture Clearly
Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.
Build Accessible, Production-Ready Frontends
Frontend work can become inconsistent, inaccessible, or difficult to maintain. This skill guides component architecture, responsive layouts, state handling, and polished user experiences.
Discover and Apply Agent Skills
Teams often lose time choosing the right workflow for a software task. This skill maps task context to focused agent skills and a practical development sequence.
Préparer des dossiers de release
par yaojingang
Les équipes de release rassemblent souvent les étapes de déploiement progressif, les notes de migration, les déclencheurs de retour arriÚre et les messages aux parties prenantes à différents endroits. Cette skill transforme ces éléments en un dossier de release structuré unique avec une orientation go/no-go.
Instrumenter les applications Azure avec Application Insights
par microsoft
Ajouter une tĂ©lĂ©mĂ©trie fiable aux applications hĂ©bergĂ©es sur Azure peut ĂȘtre difficile selon les frameworks et les modĂšles de dĂ©ploiement. Cette compĂ©tence fournit des conseils concis de configuration dâApplication Insights, des rĂ©fĂ©rences SDK et des modĂšles de configuration Azure.
Déployer des charges de travail Kubernetes avec des étapes guidées
par sickn33
Les releases Kubernetes nĂ©cessitent de nombreux artefacts et contrĂŽles coordonnĂ©s. Cette compĂ©tence guide la prĂ©paration des conteneurs, les manifestes, les charts Helm, le service mesh, la sĂ©curitĂ©, lâobservabilitĂ© et la validation du dĂ©ploiement.
Ajouter des patterns dâobservabilitĂ© Python
par 0xDarkMatter
Les services Python manquent souvent de patterns cohérents pour la journalisation, les métriques et le traçage. Cette compétence fournit des exemples pratiques avec structlog, Prometheus et OpenTelemetry pour les applications de production.
Résoudre plus rapidement les incidents DevOps
par sickn33
Les incidents de production nĂ©cessitent un triage rapide entre les journaux, les mĂ©triques, les traces et les plateformes cloud. Cette compĂ©tence guide le dĂ©bogage DevOps structurĂ©, lâanalyse des causes racines et la planification de la reprise.
Optimiser les performances des applications
par sickn33
Les systĂšmes lents nuisent aux utilisateurs, Ă la fiabilitĂ© et aux coĂ»ts cloud. Cette compĂ©tence aide Ă diagnostiquer les goulots dâĂ©tranglement, Ă concevoir des tests et Ă planifier des optimisations mesurĂ©es.