Star200+

Pre-install eval

Bybit Trading Bot Integrated With TradingView Webhook Alerts Eval report.

A machine-readable install decision for agents: task fit, Trust Score, Audit Score, install safety, permission surface, and a concrete validation plan before this skill touches a workspace.

FailedHigh riskBLOCK Policy
61
Eval report
70
Trust
61
Audit
45
Agent safety

do not auto install

Audit score: Risky

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate Bybit Trading Bot Integrated With TradingView Webhook Alerts before installing it in an agent workflow
  • finance
  • Coding agents workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add Mtemi/Bybit-Trading-Bot-Integrated-with-TradingView-Webhook-Alerts

Install command safety

92

pass

standard package or runtime install path

  • npx skills add Mtemi/Bybit-Trading-Bot-Integrated-with-TradingView-Webhook-Alerts

Trust score

70

warn

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

  • Manual review
  • 506 GitHub stars
  • Unknown

Audit score

61

fail

Risky

  • License is unclear

Agent safety gate

45

fail

This skill should not be selected by an agent without explicit human security review.

  • Do not auto-install. Inspect the source, dependencies, and permission surface first.
  • Audit risk exceeds the requested agent policy

License clarity

42

warn

Unknown

  • Unknown

Permission surface

72

warn

filesystem or document access, network or browser access

  • Network access: medium
  • Filesystem access: medium

Validation plan

What the agent should do next

  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.

Do not use when

Conditions that require another skill

  • teams that require actively maintained dependencies
  • production agents without a repository review
  • Repository looks stale
  • Audit risk risky exceeds max_risk=medium
  • License is unclear
  • Repository appears stale

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

90

Metadata includes enough usage and workflow context

Recent maintenance

fail

22

4y since push

Alternatives available

pass

82

Alternative skills are available for comparison.