Migrate Workflows to Factory
Moving an existing agent workflow into Factory can create duplicate roles, broken paths, or conflicting handoffs. This skill guides a focused migration into an existing Factory repository and validates the resulting configuration.
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "migrate-to-factory" from https://skillstore.io/skills/warpdotdev-migrate-to-factory.md and its manifest at https://skillstore.io/api/skills/warpdotdev-migrate-to-factory/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 « migrate-to-factory ». Migrate the release-triage workflow from the supplied skill directory into the existing Factory repository.
Résultat attendu:
The workflow was assigned to the existing triage agent. Shared guidance was added under the shared skills directory, source files remained unchanged, and Factory validation passed.
Utilisation de « migrate-to-factory ». Move this skill and its templates into the Factory repository, but do not add new agents unless necessary.
Résultat attendu:
Utilisation de « migrate-to-factory ». Review this migration for conflicting ownership before editing.
Résultat attendu:
The migration paused because the requested workflow overlaps with the review agent and the existing code-review handoff. User clarification is required before changes can be made.
All ten static findings are false positives caused by Markdown code spans, a documentation URL, or a safe scope instruction in SKILL.md. The file still requires normal review because it directs edits inside a Factory repository and handles untrusted migration sources.
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/warpdotdev-migrate-to-factory/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/warpdotdev-migrate-to-factory?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/warpdotdev-migrate-to-factory?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/warpdotdev-migrate-to-factory/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/warpdotdev-migrate-to-factory.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>warpdotdev. (2026). migrate-to-factory security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/warpdotdev-migrate-to-factory/audits/1@techreport{warpdotdev-warpdotdev-migrate-to-factory-2026,
author = {warpdotdev},
title = {migrate-to-factory security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/warpdotdev-migrate-to-factory/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: "migrate-to-factory security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "warpdotdev"
date-released: "2026-09-18"
url: "https://skillstore.io/skills/warpdotdev-migrate-to-factory/audits/1"
identifiers:
- type: other
value: "skillstore:warpdotdev-migrate-to-factory:audit:1"
description: "Skillstore immutable audit report identifier"
Move an existing agent workflow into a Factory repository while preserving role ownership and handoff boundaries.
Review shared and role-specific guidance, then place each resource where the Factory agents can use it without duplication.
Create a focused migration proposal with adapted paths, validation results, and clearly identified unresolved source behavior.
Migrate the skill at [source path] into the existing Factory repository at [Factory path]. First identify the workflow entry point and report any missing context.
Review [source paths] and the current Factory agents. Recommend which responsibilities belong in shared skills, agent-scoped skills, or new agents before making edits.
Migrate [source skill] and its referenced scripts, templates, assets, and references into [Factory path]. Keep source files read-only and adapt all relative references.
Migrate [workflow] into [Factory path]. Reuse existing roles where possible, preserve unrelated customization, stop on ambiguous conflicts, validate the complete Factory root, and report every changed file and unresolved limitation.
Auteur
warpdotdevLicence
MIT
Révision Skillstore
r1
Avis de version
L’auteur n’a déclaré aucune version.
Réf
c5e997603f469d8796c1290f007a735780780183
Récence de maintenance
18/09/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
📄 SKILL.md
Compare Decisions with an AI Council
Complex decisions can suffer from narrow analysis and hidden assumptions. This skill coordinates diverse agents, compares their evidence, and produces one actionable recommendation.
Plan Features With Living Specs
Substantial feature work can become ambiguous when product intent, technical decisions, and implementation drift apart. This skill guides agents through practical product and technical specifications that stay aligned with shipped work.
Resolve Pull Request Feedback Safely
Pull request feedback can be difficult to track, implement, and answer consistently. This skill guides each decision, validates accepted changes, and previews GitHub responses before posting.
Write Clear Product Specifications
Turn ambiguous feature requests into structured product specifications that align design, engineering, and review. This skill defines user-visible behavior, scope, references, open questions, and handoff details in a consistent PRODUCT.md format.
Diagnose CI Failures Faster
CI failures can hide the first useful error among checks, logs, and repeated noise. This skill gathers relevant GitHub evidence and produces a prioritized plan for repair.
Delegate Broad Codebase Research
Large investigations can flood the primary agent context with irrelevant files and logs. This skill delegates read-only research and returns concise conclusions with cited evidence.
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.
Créer des plugins Claude Code
par C0ntr0lledCha0s
Créer des plugins Claude Code exige une structure correcte, une validation, une documentation et un empaquetage sécurisé. Cette skill guide les utilisateurs à travers l’architecture des plugins, les modèles, la validation et les workflows de publication.
Gérer les mises à jour et les audits des dépendances
par 89jobrien
Les mises à jour de dépendances peuvent masquer des vulnérabilités, des problèmes de licence et des changements incompatibles. Cette compétence guide les audits, les mises à niveau sûres et les rapports avec les gestionnaires de packages courants.
Créer des hooks d'automatisation Claude Code
par C0ntr0lledCha0s
Les hooks Claude Code peuvent automatiser les vérifications, le formatage et l'application de politiques, mais des scripts de hooks non sécurisés peuvent affecter les fichiers ou les commandes locaux. Cette compétence guide les utilisateurs dans la conception, la validation et la maintenance structurées de hooks.
Écrire des règles Hookify pour Claude Code
par anthropics
Les règles de hooks peuvent être difficiles à écrire correctement pour les événements bash, file, stop et prompt. Cette compétence fournit à Claude, Codex et Claude Code des conseils pratiques pour créer et tester des règles Hookify.
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.