Pre-install eval

serial 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
67
Eval report
69
Trust
76
Audit
48
Agent safety

manual review

Test manually in an isolated workspace and compare against safer alternatives.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

70

warn

Task fit is weak; compare alternatives before selecting.

  • Evaluate serial before installing it in an agent workflow
  • automation
  • Browser automation workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add zhinkgit/embeddedskills --skill serial

Install command safety

92

pass

standard package or runtime install path

  • npx skills add zhinkgit/embeddedskills --skill serial

Trust score

69

warn

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

  • Manual review
  • 625 GitHub stars
  • MIT

Audit score

76

warn

Needs review

  • The SKILL.md front matter description is parsed as '>-' in the metadata, which may indicate a YAML parsing quirk, though the full description is present in the document.

Agent safety gate

48

warn

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

pass

MIT

  • MIT

Permission surface

62

warn

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • 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 need a vendor-supported SLA
  • production agents without a repository review
  • The SKILL.md front matter description is parsed as '>-' in the metadata, which may indicate a YAML parsing quirk, though the full description is present in the document.
  • High-risk permission hints: Shell or command execution
  • The documentation is primarily in Chinese, which could be a barrier for non-Chinese-speaking users, but this does not affect functionality.
  • The skill writes to .embeddedskills/config.json and state.json, which could potentially conflict with other skills using the same files, though this is a minor concern.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

1mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.