OpenAgentSkill
GitHub200+

Évaluation avant installation

Browsernode 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.

ÉchouĂ©Risque Ă©levĂ©Bloquer Politique
71
Rapport d’évaluation
80
Confiance
74
Audit
54
Sécurité Agent

do not auto install

Install path: No install command or repository handoff is available.

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 Browsernode before installing it in an agent workflow
  • agent-frameworks
  • Browser automation workflows; Claude Code teams; teams that value GitHub adoption signals

Chemin d’installation

20

ÉchouĂ©

No install command or repository handoff is available.

SĂ©curitĂ© de la commande d’installation

92

Validé

Chemin d’installation standard de package ou runtime

Score de confiance

80

Avertissement

Good trust signals with a few areas worth checking before rollout.

  • Liste solide
  • 1.1K stars GitHub
  • MIT

Score d’audit

74

Avertissement

Revue nécessaire

  • Repository appears stale

ContrÎle de sécurité Agent

54

Avertissement

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

  • Skill source structure is not confirmed in the registry. Inspect the source and identify valid skill instructions before proposing an installation. A repository URL or GitHub stars do not prove installability.

Clarté de licence

86

Validé

MIT

  • MIT

Surface de permissions

72

Avertissement

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

  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

  • teams that require actively maintained dependencies
  • production agents without a repository review
  • Repository looks stale
  • Repository appears stale
  • Skill source structure is not confirmed in the registry. Inspect the source and identify valid skill instructions before proposing an installation. A repository URL or GitHub stars do not prove installability.
  • Financial research output is not financial advice; require human review before any live investment decision

Vérifications complémentaires

Signaux de confiance derriÚre la décision

Complétude README/SKILL.md

Avertissement

74

Les métadonnées publiques nécessitent davantage de contexte README/SKILL.md

Maintenance récente

ÉchouĂ©

38

1 ans depuis le dernier push

Alternatives disponibles

Validé

82

Alternative skills are available for comparison.