Ăvaluation avant installation
Markserv 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.
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
Adéquation à la tùche
84
Task wording matches this skill metadata.
- Evaluate Markserv before installing it in an agent workflow
- document-processing
- Document processing workflows; Claude Code teams; teams that value GitHub adoption signals
Chemin dâinstallation
20
No install command or repository handoff is available.
SĂ©curitĂ© de la commande dâinstallation
92
Chemin dâinstallation standard de package ou runtime
Score de confiance
76
Good trust signals with a few areas worth checking before rollout.
- Liste solide
- 603 stars GitHub
- MIT
Score dâaudit
76
Revue nécessaire
- Financial research output is not financial advice; require human review before any live investment decision
ContrÎle de sécurité Agent
48
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
MIT
- MIT
Surface de permissions
62
shell or command execution, filesystem or document access
- Shell or command execution: high
- 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
- Environnements fortement conformes sans revue interne de sécurité
- No major risk signals from current metadata
- Indices de permissions à haut risque : exécution shell ou de commande
- Financial research output is not financial advice; require human review before any live investment decision
- 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.
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âusage et de workflow
Maintenance récente
Avertissement62
7 mois depuis le dernier push
Alternatives disponibles
Validé82
Alternative skills are available for comparison.