Star200+

脡valuation avant installation

AI HealthCare Assistant Rapport d鈥櫭﹙aluation.

Une d茅cision d鈥檌nstallation lisible par machine pour les Agents : ad茅quation 脿 la t芒che, Trust Score, Audit Score, s茅curit茅 d鈥檌nstallation, surface de permissions et plan de validation concret avant de toucher l鈥檈space de travail.

Revue n茅cessaireRisque moyenRevoir Politique
72
Rapport d鈥櫭﹙aluation
79
Confiance
79
Audit
51
S茅curit茅 Agent

Revue manuelle

Test manually in an isolated workspace and compare against safer alternatives.

Gates requis

V茅rifications qu鈥檜n Agent doit r茅ussir avant installation

Ouvrir JSON

Ad茅quation 脿 la t芒che

94

Valid茅

Task wording matches this skill metadata.

  • Evaluate AI HealthCare Assistant before installing it in an agent workflow
  • web3-analytics
  • RAG and knowledge workflows; Claude Code teams; builders willing to evaluate younger projects

Chemin d鈥檌nstallation

92

Valid茅

Install handoff is available.

  • npx skills add ahlem-phantom/AI-HealthCare-Assistant

S茅curit茅 de la commande d鈥檌nstallation

92

Valid茅

Chemin d鈥檌nstallation standard de package ou runtime

  • npx skills add ahlem-phantom/AI-HealthCare-Assistant

Score de confiance

79

Avertissement

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

  • Liste solide
  • 147 stars GitHub
  • Apache-2.0

Score d鈥檃udit

79

Avertissement

Revue n茅cessaire

  • Financial research output is not financial advice; require human review before any live investment decision

Contr么le de s茅curit茅 Agent

51

Avertissement

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

  • Test manually in an isolated workspace and compare against safer alternatives.
  • Indices de permissions 脿 haut risque : Secrets or environment access

Clart茅 de licence

86

Valid茅

Apache-2.0

  • Apache-2.0

Surface de permissions

86

Valid茅

Acc猫s au syst猫me de fichiers ou aux documents

  • Network access: medium
  • Filesystem access: medium
  • Secrets or environment access: high

Plan de validation

Ce que l鈥橝gent 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
  • Environnements fortement conformes sans revue interne de s茅curit茅
  • No major risk signals from current metadata
  • Indices de permissions 脿 haut risque : Secrets or environment access
  • Financial research output is not financial advice; require human review before any live investment decision
  • 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

Valid茅

90

Les m茅tadonn茅es incluent suffisamment de contexte d鈥檜sage et de workflow

Maintenance r茅cente

Avertissement

76

4 mois depuis le dernier push

Alternatives disponibles

Valid茅

82

Alternative skills are available for comparison.