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

Ieee Cover

skill-tenwalk-ieee-skills-ieee-cover · by TenWalk

>-

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

Install

$ agentstack add skill-tenwalk-ieee-skills-ieee-cover

✓ 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-tenwalk-ieee-skills-ieee-cover)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo 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 Ieee Cover? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

IEEE Cover Letter and Significance Framing

Use this skill to write the editor-facing letter that accompanies an IEEE submission. The cover letter should help the editor see fit, novelty, evidence, and compliance quickly; it is not a second abstract and not a reviewer response.

Core stance

  • Editor first. State why the manuscript belongs in the target journal or special issue, what

the technical contribution is, and why the evidence is sufficient.

  • Specific beats promotional. Use concrete contribution/evidence language; avoid "highly

novel", "breakthrough", and unsupported impact claims.

  • Do not over-disclose reviewer-response detail. For a revision, summarize the main changes and

point to the response letter; do not replay every comment.

  • Compliance matters. Include originality, non-duplication, conflicts, ethics/data/code

statements, and suggested/opposed reviewers only when the journal asks or the user supplies them.

  • No fabricated names or claims. Never invent editor names, reviewer names, manuscript IDs,

funding statements, conflicts, or data availability.

When to open extra files

| File | Open when | |---|---| | [references/cover-letter-template.md](references/cover-letter-template.md) | Drafting a new-submission or revised-submission cover letter | | [references/significance-framing.md](references/significance-framing.md) | Writing the significance/fit paragraph for JSAC/TWC/TCOM/WCL/CL, special issues, or interdisciplinary framing |

For target-journal routing, also use ieee-writing's journal-fit.md when needed. For reviewer responses use ieee-response.

Intake

  • target journal or special issue;
  • manuscript title and paper type;
  • one-sentence contribution;
  • 2-4 evidence points: theorem/proof, algorithm, simulation, testbed, dataset, or measured result;
  • status: new submission, revision, transfer, or resubmission after rejection;
  • manuscript ID, editor name, suggested reviewers/conflicts, and required declarations if available.

If target, title, contribution, or evidence is missing, draft with placeholders and list the missing items.

Workflow

  1. Write a fit sentence: target journal/special issue + technical scope + why the paper belongs.
  2. State the contribution plainly: one paragraph, no hype, no citations unless the journal

expects them.

  1. Tie evidence to claims: theorem/proof/simulation/testbed/complexity and the target-specific

reason it is enough.

  1. For revisions, summarize changes: new experiments, clarified assumptions, softened claims,

added comparisons, improved figures.

  1. Add compliance paragraph: originality, exclusive submission, conflicts, data/code/ethics,

reviewer suggestions only from supplied facts.

  1. Close briefly and keep the letter usually under one page.

Output format

  1. Cover letter: copy-pasteable editor-facing letter.
  2. Significance / fit note: 3-5 bullets explaining why the framing matches the target journal.
  3. Compliance checklist: required statements and whether the user supplied them.
  4. Missing inputs: exact editor name, manuscript ID, reviewer names, declarations, or evidence.

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.