Pre-install eval

docx 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
70
Eval report
70
Trust
80
Audit
52
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 docx before installing it in an agent workflow
  • automation
  • Document processing workflows; Claude Code teams; teams that value GitHub adoption signals

Install path

92

pass

Install handoff is available.

  • npx skills add axoviq-ai/synthadoc --skill docx

Install command safety

92

pass

standard package or runtime install path

  • npx skills add axoviq-ai/synthadoc --skill docx

Trust score

70

warn

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

  • Manual review
  • 1.5K GitHub stars
  • AGPL-3.0-or-later

Audit score

80

warn

Needs review

  • SKILL.md does not mention that extracted Word document content should be treated as untrusted data, which is relevant for agents that might interpret document text as instructions.

Agent safety gate

52

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

AGPL-3.0-or-later

  • AGPL-3.0-or-later

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
  • SKILL.md does not mention that extracted Word document content should be treated as untrusted data, which is relevant for agents that might interpret document text as instructions.
  • High-risk permission hints: Shell or command execution
  • SKILL.md documents paragraph extraction but does not note that tables, headers, footers, and text boxes are ignored.
  • No guidance on handling unusually large or malformed .docx files; python-docx parsing can consume significant memory if given a crafted or zip-bomb-like document.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

warn

70

Public metadata needs stronger README/SKILL.md context

Recent maintenance

pass

100

21d since push

Alternatives available

pass

82

Alternative skills are available for comparison.