AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Top Cs Polishing

skill-zhiming33416-top-cs-paper-skills-top-cs-polishing · by zhiming33416

Polish, translate, tighten, structurally revise, or diagnose existing computer-science manuscript prose and LaTeX for WWW, ICLR, ICML, or a generic venue while preserving evidence. Use for Chinese-to-English academic rewriting, paragraph flow, section-level revision, claim calibration, concision, terminology consistency, reducing generic AI prose, revision ledgers, and LaTeX layout or float-place…

No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-zhiming33416-top-cs-paper-skills-top-cs-polishing

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-zhiming33416-top-cs-paper-skills-top-cs-polishing)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Top Cs Polishing? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Top CS Paper Polishing

Route the request

  1. Read manifest.yaml and every always_load path.
  2. Detect and state venue, paper type, section, language, revision mode, artifact scope, evidence state, submission stage, citation verification, and figure handoff.
  3. Load only the static fragments mapped to those values.
  4. Open deeper references only when an on_demand condition applies.
  5. Use generic for unsupported venue/year combinations and warn that official rules require verification.

Execute

  1. Extract immutable facts: quantities, comparison direction, conditions, citations, equations, uncertainty, and explicit boundaries.
  2. Build or update the terminology ledger for multi-paragraph work.
  3. Diagnose in this order: framing, rhetorical structure, evidence connection, terminology, and sentence form.
  4. Respect the selected revision mode: keep light-edit local, permit reordering in structural-revision, and prove information preservation in compression.
  5. Revise in the order paper role -> section job -> paragraph logic -> claim/evidence/boundary -> sentence form.
  6. Record every material change and any claim-strength, citation, or figure-reference shift in the revision ledger.
  7. Verify preserved facts, citations, LaTeX, terminology, and reader workflow; report what was compiled, rendered, structurally checked, or not verified.

Preserve scientific meaning and never silently strengthen novelty, causality, generality, or significance. Preserve LaTeX commands, labels, citations, equations, and comments unless a necessary change is explicitly reported. For a supplied LaTeX project, run scripts/check_latex_project.py when an engine is available; never enable shell escape or write build artifacts into the source project.

When auditing figures, check claim, caption, callout, terminology, and label alignment only. Return a corrected handoff brief when necessary; do not render or restyle the figure. Metadata verification does not establish that a cited source supports the manuscript claim.

For page-layout or float-placement requests, load references/latex-layout.md, compile to an isolated output directory, and inspect rendered pages before and after. Do not judge layout from source alone.

Default to Chinese revision notes and English revised prose. Return paste-ready text, not only advice.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.