Pre-install eval

vietnamese-tech-writing 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
63
Eval report
64
Trust
72
Audit
40
Agent safety

do not auto install

Permission surface: shell or command execution, filesystem or document access

Required gates

Checks an agent must pass before install

Open JSON

Task fit

84

pass

Task wording matches this skill metadata.

  • Evaluate vietnamese-tech-writing before installing it in an agent workflow
  • research
  • GitHub automation workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add trussary/vietnamese-language-skill --skill vietnamese-tech-writing

Install command safety

92

pass

standard package or runtime install path

  • npx skills add trussary/vietnamese-language-skill --skill vietnamese-tech-writing

Trust score

64

warn

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

  • Manual review
  • 77 GitHub stars
  • MIT

Audit score

72

warn

Needs review

  • Permission surface may require sandboxing

Agent safety gate

40

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

48

fail

shell or command execution, filesystem or document access

  • Shell or command execution: high
  • Browser automation: medium
  • 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
  • SKILL.md does not explicitly define an output format or deliverable structure for the agent (e.g., revised text plus explanations), which may lead to inconsistent agent responses.
  • High-risk permission hints: Shell or command execution
  • Permission surface may require sandboxing
  • The skill would benefit from an explicit 'when not to use' or limitations section to distinguish technical/product documentation from general marketing copy and legal advice.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

88

2mo since push

Alternatives available

pass

82

Alternative skills are available for comparison.