OpenAgentSkill
GitHub200+

Pre-install eval

pocky-xhs-ai-content 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.

Needs reviewMedium riskREVIEW Policy
65
Eval report
65
Trust
71
Audit
59
Agent safety

manual review

Require human approval before installing into a real workspace.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate pocky-xhs-ai-content before installing it in an agent workflow
  • automation
  • Browser automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add zaoshangduziteng/pocky-xhs-ai-content --skill pocky-xhs-ai-content

Install command safety

92

pass

standard package or runtime install path

  • npx skills add zaoshangduziteng/pocky-xhs-ai-content --skill pocky-xhs-ai-content

Trust score

65

warn

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

  • Manual review
  • 13 GitHub stars
  • MIT

Audit score

71

warn

Needs review

  • The submitted skill directory does not include the referenced scripts/render_pages.js, scripts/validate_pngs.py, assets/, or docs/images; if these are required, the described rendering/QA workflow is incomplete in this submission.

Agent safety gate

59

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • The submitted skill directory does not include the referenced scripts/render_pages.js, scripts/validate_pngs.py, assets/, or docs/images; if these are required, the described rendering/QA workflow is incomplete in this submission.

License clarity

86

pass

MIT

  • MIT

Permission surface

100

pass

no high-risk permission surface in public metadata

  • Network 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 need a vendor-supported SLA
  • production agents without a repository review
  • Low GitHub adoption signal
  • The submitted skill directory does not include the referenced scripts/render_pages.js, scripts/validate_pngs.py, assets/, or docs/images; if these are required, the described rendering/QA workflow is incomplete in this submission.
  • SKILL.md lacks a setup/prerequisites section: it does not state which runtimes/dependencies (Node.js, Python, image libraries) are needed before running the scripts.
  • The skill collects facts and screenshots from official websites but does not explicitly instruct the agent to treat scraped page content as untrusted data (prompt-injection guardrail).

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

76

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.