Évaluation avant installation
craft-garnish Rapport d’évaluation.
Une décision d’installation lisible par machine pour les Agents : adéquation à la tâche, Trust Score, Audit Score, sécurité d’installation, surface de permissions et plan de validation concret avant de toucher l’espace de travail.
Revue manuelle
Test manually in an isolated workspace and compare against safer alternatives.
Gates requis
Vérifications qu’un Agent doit réussir avant installation
Adéquation à la tâche
84
Task wording matches this skill metadata.
- Evaluate craft-garnish before installing it in an agent workflow
- Design et création
- Design and creative workflows; Claude Code teams; builders willing to evaluate younger projects
Chemin d’installation
92
Install handoff is available.
- npx skills add michtio/craftcms-claude-skills --skill craft-garnish
Sécurité de la commande d’installation
92
Chemin d’installation standard de package ou runtime
- npx skills add michtio/craftcms-claude-skills --skill craft-garnish
Score de confiance
69
Potentially useful, but at least one trust signal needs human inspection.
- Revue manuelle
- 78 stars GitHub
- MIT
Score d’audit
74
Revue nécessaire
- The description trigger list is extremely long and may cause the skill to be loaded in borderline cases; organizing triggers into clear categories in the description could reduce over-triggering and improve scannability.
Contrôle de sécurité Agent
54
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- Test manually in an isolated workspace and compare against safer alternatives.
- The description trigger list is extremely long and may cause the skill to be loaded in borderline cases; organizing triggers into clear categories in the description could reduce over-triggering and improve scannability.
Clarté de licence
86
MIT
- MIT
Surface de permissions
72
filesystem or document access, network or browser access
- Browser automation: medium
- Network access: medium
- Filesystem access: medium
Plan de validation
Ce que l’Agent doit faire ensuite
- 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
- 2Install in an isolated workspace or sandbox with no production secrets available.
- 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
- 4Compare the selected skill against at least one alternative when the eval status is review or failed.
- 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.
Ne pas utiliser quand
Conditions exigeant une autre skill
- Équipes qui nécessitent un SLA soutenu par le fournisseur
- production agents without a repository review
- The description trigger list is extremely long and may cause the skill to be loaded in borderline cases; organizing triggers into clear categories in the description could reduce over-triggering and improve scannability.
- The SKILL.md excerpt ends with an incomplete 'Task examples:' section. If the actual file is truncated, the missing examples should be completed to preserve the skill's practical guidance.
- Quality score needs review
- GitHub adoption: 78 GitHub stars
Vérifications complémentaires
Signaux de confiance derrière la décision
Complétude README/SKILL.md
Validé86
Les métadonnées incluent suffisamment de contexte d’usage et de workflow
Maintenance récente
Validé88
1 mois depuis le dernier push
Alternatives disponibles
Validé82
Alternative skills are available for comparison.