Évaluation avant installation

api-design 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 nécessaireRisque moyenRevoir Politique
69
Rapport d’évaluation
70
Confiance
76
Audit
56
Sécurité Agent

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

Ouvrir JSON

Adéquation à la tâche

84

Validé

Task wording matches this skill metadata.

  • Evaluate api-design 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

Validé

Install handoff is available.

  • npx skills add majiayu000/spellbook --skill api-design

Sécurité de la commande d’installation

92

Validé

Chemin d’installation standard de package ou runtime

  • npx skills add majiayu000/spellbook --skill api-design

Score de confiance

70

Avertissement

Potentially useful, but at least one trust signal needs human inspection.

  • Revue manuelle
  • 272 stars GitHub
  • MIT

Score d’audit

76

Avertissement

Revue nécessaire

  • The SKILL.md references 'OpenAPI 3.2' but the current stable version is 3.1.x; 3.2 may be in development or not widely adopted, which could confuse users.

Contrôle de sécurité Agent

56

Avertissement

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

  • Test manually in an isolated workspace and compare against safer alternatives.
  • The SKILL.md references 'OpenAPI 3.2' but the current stable version is 3.1.x; 3.2 may be in development or not widely adopted, which could confuse users.

Clarté de licence

86

Validé

MIT

  • MIT

Surface de permissions

74

Avertissement

network or browser access, database access

  • Network access: medium
  • Filesystem access: medium
  • Database access: medium

Plan de validation

Ce que l’Agent doit faire ensuite

  1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
  2. 2Install in an isolated workspace or sandbox with no production secrets available.
  3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
  4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
  5. 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 SKILL.md references 'OpenAPI 3.2' but the current stable version is 3.1.x; 3.2 may be in development or not widely adopted, which could confuse users.
  • The 'No backwards compatibility' principle is aggressive and may not suit all contexts; it could be presented with caveats.
  • Quality score needs review
  • Stars/forks activity: 272 stars, 26 forks; issue activity unavailable in current metadata

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.