rankup Eval
===========

Status: failed
Score: 66/100
Risk: high
Decision: do_not_auto_install
Policy: block
Reason: Install path: No install command or repository handoff is available.

Install:


Required checks:
- PASS Task fit: Task wording matches this skill metadata.
- FAIL Install path: No install command or repository handoff is available.
- PASS Install command safety: standard package or runtime install path
- WARN Trust score: Potentially useful, but at least one trust signal needs human inspection.
- WARN Audit score: Needs review
- WARN Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- PASS License clarity: MIT
- FAIL Permission surface: shell or command execution, filesystem or document access

Warnings:
- Trust score: Potentially useful, but at least one trust signal needs human inspection.
- Audit score: Needs review
- Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context
- High-risk permission hints: Shell or command execution
- Permission surface may require sandboxing
- The tracked source changed or could not be synchronized. Review the current source before installing.
- The SKILL.md is extremely long and dense, which may make it difficult for an agent to parse and follow in a single context window. The description field is also very verbose, potentially consuming excessive tokens.
- The skill relies on many external scripts and reference files (e.g., scripts/*.mjs, references/*.md) that are not fully visible in the excerpt. Ensure all dependencies are included and documented in the repository.
- The skill mentions 'OpenCLI' and browser automation, which may require specific environment setup. The SKILL.md does not clearly state prerequisites or fallback behavior if these tools are unavailable.
- Quality score needs review
- Permission surface needs review: shell or command execution, filesystem or document access

Validation plan:
1. Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. Install in an isolated workspace or sandbox with no production secrets available.
3. Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. Compare the selected skill against at least one alternative when the eval status is review or failed.
5. Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when:
- teams that need a vendor-supported SLA
- production agents without a repository review
- The SKILL.md is extremely long and dense, which may make it difficult for an agent to parse and follow in a single context window. The description field is also very verbose, potentially consuming excessive tokens.
- No OpenAgentSkill engagement data yet
- High-risk permission hints: Shell or command execution
- Permission surface may require sandboxing
- The tracked source changed or could not be synchronized. Review the current source before installing.
- The skill relies on many external scripts and reference files (e.g., scripts/*.mjs, references/*.md) that are not fully visible in the excerpt. Ensure all dependencies are included and documented in the repository.

URLs:
- Skill: https://www.openagentskill.com/skills/yan-labs-rankup
- Audit: https://www.openagentskill.com/skills/yan-labs-rankup/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=yan-labs-rankup