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

Ieee Citation

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

>-

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

Install

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

✓ 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-citation)

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 Citation? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

IEEE Citation and Reference Formatting

Use this skill to turn raw references, a .bib file, DOIs, or a messy bibliography into correct IEEE-style entries and in-text citations, and to set up Index Terms and the IEEEtran bibliography.

Core stance

  • Never fabricate metadata. Do not invent a DOI, volume, issue, page range, year, or venue.

If a field is missing, output [MISSING: volume] (or similar) and ask the user, or leave the BibTeX field empty rather than guessing.

  • Order by first appearance, not alphabetically. IEEE numbers references [1], [2], ... in

the order they are first cited in the text; the reference list follows that same order.

  • Abbreviate journal and conference names per IEEE (e.g., *IEEE Transactions on Pattern

Analysis and Machine IntelligenceIEEE Trans. Pattern Anal. Mach. Intell.*). If unsure of an abbreviation, flag it rather than inventing one.

  • Defer to the target journal's Author Kit where it differs (some allow DOIs, some omit them;

some want month, some do not).

When to open extra files

| File | Open when | |---|---| | [references/ieee-reference-format.md](references/ieee-reference-format.md) | Formatting any reference entry (journal, conference, book, chapter, thesis, online, standard, patent, preprint) or in-text citations | | [references/ieeetran-latex.md](references/ieeetran-latex.md) | Setting up IEEEtran: \bibliographystyle{IEEEtran}, .bib entry types/fields, \cite usage, Index Terms, EDICS, common BibTeX pitfalls |

Quick rules (most common needs)

  • In-text: square brackets, on the line (not superscript): "as shown in [3]". Group as

"[1], [2]" or a range "[4]–[7]". Cite in numerical order at each point.

  • Do not use the number as a noun: prefer "the method of [12]" / "Smith et al. [12]" over

"in [12], they...".

  • Author names: initials then surname — "J. K. Author". Up to six names; for more, list the

first followed by "et al.".

  • One reference = one list entry, numbered in brackets, hanging indent in IEEEtran (automatic).

Workflow

  1. Collect the references (text, .bib, DOIs). Identify the type of each (journal,

conference, book, ...).

  1. Map citation order: scan the manuscript for first-appearance order; renumber accordingly.
  2. Format each entry using references/ieee-reference-format.md; abbreviate venue names.
  3. Flag gaps: mark any missing/uncertain field; never fill by guess.
  4. In-text pass: ensure every [n] resolves, ordering is by appearance, and there are no

orphan or unused entries.

  1. Output the formatted list (and a .bib if the user uses LaTeX), plus a list of flags.

Output format

  1. References: the numbered IEEE-formatted list (plain text), or a .bib block for IEEEtran.
  2. In-text notes: any citation-order or phrasing fixes needed in the body.
  3. Flags: every missing or uncertain field the author must verify.
  4. (If requested) Index Terms: 5–8 alphabetical terms.
  5. (If submitting to CL or another EDICS journal) EDICS: the best-fitting category code(s) from

the journal's current list — never invent a code; tell the user to confirm against the live list.

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.