Pre-install eval
ads 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.
manual review
Test manually in an isolated workspace and compare against safer alternatives.
Required gates
Checks an agent must pass before install
Task fit
70
Task fit is weak; compare alternatives before selecting.
- Evaluate ads before installing it in an agent workflow
- automation
- Browser automation workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add aAAaqwq/AGI-Super-Team --skill ads
Install command safety
92
standard package or runtime install path
- npx skills add aAAaqwq/AGI-Super-Team --skill ads
Trust score
65
Potentially useful, but at least one trust signal needs human inspection.
- Manual review
- 91 GitHub stars
- MIT
Audit score
73
Needs review
- Financial research output is not financial advice; require human review before any live investment decision
Agent safety gate
41
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- Test manually in an isolated workspace and compare against safer alternatives.
- High-risk permission hints: Shell or command execution
License clarity
86
MIT
- MIT
Permission surface
62
shell or command execution, network or browser access
- Shell or command execution: high
- Browser automation: medium
- Network access: medium
Validation plan
What the agent should do next
- 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.
Do not use when
Conditions that require another skill
- teams that need a vendor-supported SLA
- production agents without a repository review
- The SKILL.md description has a formatting issue: the first line ends with 'Google, Meta' and the next line starts a new sentence, causing a truncated description in the metadata. This could be cleaned up for clarity.
- High-risk permission hints: Shell or command execution
- Financial research output is not financial advice; require human review before any live investment decision
- The skill relies on external references (benchmarks, bidding strategies, etc.) that are not fully included in the excerpt, but they are referenced as files in the repository. This is acceptable as long as they are present in the full submission.
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
warn70
Public metadata needs stronger README/SKILL.md context
Recent maintenance
pass88
2mo since push
Alternatives available
pass82
Alternative skills are available for comparison.