cite-placement

REVIEW · 57
Registry indexed

>-

Verified installs0
Stars47
Version1.0.0
Quality63/100 · Promising
Trust57/100 · Do not auto-install
Audit74/100 · Needs review

Supply asset profile

Research and knowledge work

Deep research, source comparison, literature review, RAG, knowledge search, and reports.

Browse track

Scenario

Document processing

I need my agent to read PDFs, extract tables, and turn documents into structured data.

Agent fit

Claude Code + CLI + Codex

Codex, Claude Code, Cursor, CLI, or custom agents.

Install

Ready

npx skills add kennethkhoocy/applied-micro-skills --skill cite-placement

Maintenance

fresh

Pushed today

Risk

Needs review

Financial research output is not financial advice; require human review before any live investment decision

GitHub quality

47

63/100 Quality · 65/100 Trust

Coverage tags

ResearchDocument processingautomationagent-skill

Review notes

Financial research output is not financial advice; require human review before any live investment decision · The SKILL.md excerpt is truncated, but the provided content is clear and well-structured.

Agent adoption scorecard

Trust, audit, and install readiness at a glance

These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.

Quality

Promising
63

Useful candidate, but compare it with alternatives before adopting.

Trust

Do not auto-install
57

Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.

Audit

Needs review
74

A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.

OpenAgentSkill Trust Score v5

Human review before install

Choose a stronger alternative or inspect the source manually before any install attempt.

CodexClaude CodeCursorOpenAgentSkill CLI

Stars

47 GitHub stars

Repo activity

47 stars, 0 forks

Maintenance

Pushed today

License

MIT

Install

npx skills add kennethkhoocy/applied-micro-skills --skill cite-placement

Install safety

standard package or runtime install path

Permission surface

shell or command execution, filesystem or document access

Agent outcomes

No agent outcome data yet

Docs

Thin public metadata

Risk summary

Review before production

  • The SKILL.md excerpt is truncated, but the provided content is clear and well-structured.
  • Financial research output is not financial advice; require human review before any live investment decision.
  • Low GitHub adoption signal
  • Quality score needs review

Install readiness

Install path available

  • Install path is available
  • Repository evidence is available
  • License is declared
  • No Agent Proven outcome evidence yet

Agent-readable metadata

Machine-readable decision data for this skill.

Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.

Open JSON

Suited tasks

  • Document processing workflows
  • Claude Code teams
  • builders willing to evaluate younger projects
  • Read uploaded files

Suited agents

CodexClaude CodeCursorOpenAgentSkill CLICLI

Install decision

Command
npx skills add kennethkhoocy/applied-micro-skills --skill cite-placement
Policy
review
Human review
yes

Trust and risk

Trust
57/100
Audit
74/100
Risk level
Needs review

Outcome loop

Endpoint
/api/agent/outcome
Event ID
resolve
Outcomes
5

Install command

npx skills add kennethkhoocy/applied-micro-skills --skill cite-placement

Do not use when

  • teams that need a vendor-supported SLA
  • production agents without a repository review
  • Low GitHub adoption signal
  • The SKILL.md excerpt is truncated, but the provided content is clear and well-structured.
  • No OpenAgentSkill engagement data yet

Agent safety v2

42/100 · Avoid automatic install

Experimentalreview

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

Test manually in an isolated workspace and compare against safer alternatives.

Resolve via API

high

Shell or command execution

Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.

medium

Browser automation

Skill may drive a browser or interact with web pages.

medium

Network access

Skill likely fetches remote pages, APIs, repositories, or external services.

medium

Filesystem access

Skill may read or write project files, documents, generated artifacts, or local workspace state.

  • High-risk permission hints: Shell or command execution
  • Financial research output is not financial advice; require human review before any live investment decision

Install targets

Install this skill in your agent workflow

Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.

skill install

OpenAgentSkill CLI

Resolve policy, run the source installer safely, and report a verified install receipt.

$ npx --yes https://github.com/Leon-Drq/openagentskill/releases/download/cli-v0.2.1/openagentskill-0.2.1.tgz install kennethkhoocy-cite-placement

Agent resolve plan

Let an agent verify fit before installing.

The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.

Open text plan

Agent should check

  • Task fit and alternatives from Resolve API.
  • Audit score, trust score, and safety policy warnings.
  • Install target compatibility for Codex, Claude Code, Cursor, or CLI.

Copy prompt

Task: Use cite-placement in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20cite-placement%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/kennethkhoocy-cite-placement/install
Install command: npx skills add kennethkhoocy/applied-micro-skills --skill cite-placement
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.

Agent handoff

Give an agent the install path, not another directory page.

Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.

Open install API

Agent prompt

Use cite-placement for this task. Review https://www.openagentskill.com/api/skills/kennethkhoocy-cite-placement/install, then install with: npx skills add kennethkhoocy/applied-micro-skills --skill cite-placement

Registry metadata

Agent-readable profile for automatic skill selection.

This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.

Open manifest

Agent fit

62/100

Document processing

Platforms

Claude Code

Audit report

Needs review · 74/100

A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.

View audit reportView eval report

Agent decision cockpit

Fallback candidate for Document processing

Prototype with this skill first; keep a fallback candidate ready.

62
Readiness
Prototype
Stage

Role in stack

Fallback candidate

Primary fit

Document processing

Trust label

Prototype first

Install path

Command ready

Use when

  • Document processing workflows
  • Claude Code teams
  • builders willing to evaluate younger projects

Evidence

  • recent repository activity
  • install command or GitHub repo available
  • 63/100 quality profile

review first

  • Low GitHub adoption signal
  • The SKILL.md excerpt is truncated, but the provided content is clear and well-structured.
  • No OpenAgentSkill engagement data yet

Implementation path

  1. 1Install it in a sandbox agent and run one Document processing task end to end.
  2. 2Compare output quality, latency, and failure behavior against at least one alternative.
  3. 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.

Trust profile

Do not auto-install

Trust Score v5 found insufficient evidence for agent installation. Treat this as discovery material, not an executable recommendation.

57
OpenAgentSkill Trust Score

GitHub adoption

CHECK

47 GitHub stars

Stars/forks activity

CHECK

47 stars, 0 forks; issue activity unavailable in current metadata

Recent maintenance

PASS

Pushed today

License clarity

PASS

MIT

Good signals

  • AI review approved
  • Install path is available
  • Repository evidence is available
  • Recently maintained repository
  • Install command has no obvious high-risk pattern
  • Outcome loop is ready but needs first real agent run

Review before install

  • The SKILL.md excerpt is truncated, but the provided content is clear and well-structured.
  • Financial research output is not financial advice; require human review before any live investment decision.
  • Low GitHub adoption signal
  • Quality score needs review
  • GitHub adoption: 47 GitHub stars
  • Stars/forks activity: 47 stars, 0 forks; issue activity unavailable in current metadata
  • README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context
  • No real agent outcome reports yet
  • Human review required before unattended installation

Recommended action

Choose a stronger alternative or inspect the source manually before any install attempt.

Quality profile

Promising candidate for agent workflows

Useful candidate, but compare it with alternatives before adopting.

63
GitHub stars
47
Freshness
Today
Install ready
Yes
License
MIT
Review before install: Low GitHub adoption signal · The SKILL.md excerpt is truncated, but the provided content is clear and well-structured.

Workflow fit

Use this skill in these scenarios

Workflow fit

Add it to a complete workflow

Alternative shortlist

Compare before you install

Similar skills that may fit this task.

Compare all

Overview

--- name: cite-placement description: >- Place pre-screened literature citations into a LaTeX or Word manuscript, or restyle the citations already in one. Three modes: (1) inline placement — inline \cite{}/\citet{}/\citep{} with a compiled references.bib, for author-date journals (APA, MLA, Harvard, Chicago author-date, IEEE, Vancouver); (2) footnote placement — full formatted \footnote{} or OOXML footnotes for legal and notes styles (Bluebook, OSCOLA, Chicago, APA, McGill) with Id./supra short forms; (3) restyle — convert existing footnote citations from one style to another. This skill is manual-invoke ONLY — trigger ONLY when the user explicitly runs /cite-placement or explicitly names the "cite-placement" skill. Do NOT auto-trigger on general citation, footnote, or reference requests. version: 1.0.0 metadata: author: Claude Code ---

# Citation Placement

Unified router for three citation workflows. A single Tkinter launcher collects inputs and writes `run_config.json`; the `"pipeline"` value selects one of three modes, each with its own detailed workflow document.

## Modes and Routing

| Mode | `pipeline` value | What it does | Workflow doc | |---|---|---|---| | Inline placement | `inline` | Places screened citations as inline `\cite{}` / `\citet{}` / `\citep{}` commands with a compiled `references.bib`. For economics, finance, and social-science journals (APA, MLA, Harvard, Chicago author-date, IEEE, Vancouver). `.tex` only. | `references/phase-details-inline.md` | | Footnote placement | `footnotes` | Places screened citations as full formatted `\footnote{}` (LaTeX) or native OOXML footnotes (Word), with one-click legal/notes style selection (Bluebook, OSCOLA, Chicago notes-bib, APA 7th, McGill) and Id./supra short-form post-processing. `.tex` or `.docx`. | `references/phase-details-footnotes.md` | | Restyle | `restyle` | Converts ALL existing footnote citations (hand-written or pipeline-placed) from one style to another. No spreadsheet required. `.tex` or `.docx`. | Restyle Pipeline section of `references/phase-details-footnotes.md` |

Read the relevant workflow document at the start of each phase.

## Launcher-First Protocol

When the user triggers this skill:

1. Run the launcher with a **10-minute timeout** (the user needs time to browse and configure), using the skill's known absolute directory as `[skill-dir]`, not the current working directory: ```bash python "[skill-dir]/scripts/launcher.py" ``` Call it via the Bash tool with `timeout: 600000`. 2. The unified GUI presents the file fields and options for all three modes and offers three run buttons — **Inline Placement**, **Footnote Placement**, and **Restyle** — plus a **Utilities** area (Strip All Citations; Regenerate / Reorder Cross-Refs, with or without an existing registry). On any run button the launcher validates inputs and writes `placement/run_config.json` in the **output file's parent directory**, then prints machine-readable status lines to stdout. 3. Parse the launcher's stdout: - `LAUNCHER_STATUS: success` — proceed. If missing or `cancelled`, stop. - `LAUNCHER_CONFIG_PATH: <path>` — the absolute path to `run_config.json`. Use this path for all subsequent phases. All paths inside the config are absolute; do not assume the config lives in the current working directory. 4. Read `run_config.json` and route on `config["pipeline"]`: - `"inline"` → run the inline placement pipeline (`references/phase-details-inline.md`). - `"footnotes"` → run the footnote placement pipeline (`references/phase-details-footnotes.md`). - `"restyle"` → run the restyle pipeline (Restyle Pipeline section of `references/phase-details-footnotes.md`). 5. **Run the selected pipeline end-to-end without asking questions or waiting for confirmation between phases.** The only pause is the Phase 4 human-in-the-loop gate in the two placement modes, and only when `auto_approve` is `false`.

### `run_config.json` shapes

The config always lives at `<output_parent>/placement/run_config.json`. The `"pipeline"` key selects the shape:

```jsonc // inline {"pipeline": "inline", "input_format": "tex", "project_folder": "...", "input_tex": "...", "input_xlsx": "...", "output_tex": "...", "citation_style": "apa|mla|harvard|chicago_author_date|chicago_notes|ieee|vancouver", "replan": false, "auto_approve": false, "citation_mode": "selective|comprehensive", "insertion_style": "prose|simple", "verify_citations": false}

// footnotes {"pipeline": "footnotes", "input_format": "tex|docx", "project_folder": "...", "input_tex": "...", "input_xlsx": "...", "output_tex": "...", "replan": false, "auto_approve": false, "citation_style": "bluebook|oscola|chicago|apa|mcgill", "citation_mode": "selective|comprehensive", "verify_citations": false}

// restyle {"pipeline": "restyle", "input_format": "tex|docx", "project_folder": "...", "input_tex": "...", "input_xlsx": null, "output_tex": "...", "current_style": "...", "target_style": "..."} ```

## Citation slots (`% CITE:`)

Drafts from the `writing-article-plans` skill mark where citations belong with typed placeholder slots, and its `assemble_manuscript.py` normalizes footnote-wrapped slots before handoff. A slot is a `% CITE:` LaTeX comment carrying a typed hint (e.g. `% CITE: meta-analysis on Y`). Slots are a `.tex` convention only — footnotes-mode `.docx` input has no slot support.

**Core rule (both placement modes).** If the input manuscript contains `% CITE:` slots, every slot MUST end the run either filled or explicitly reported as unfilled with a reason. Silent slot survival is a pipeline failure. Slots are author-declared citation demands, so `citation_mode: "selective"` governs only free placements and never skips a slot.

Three slot forms reach this skill: 1. **Bare comment** — `% CITE: <hint>` on its own line or at the end of a line. 2. **Footnote-wrapped, two-line** (`\footnote{%` / `% CITE: <hint>` / `}`) — the normal post-assembly form (brace-safe). 3. **Footnote-wrapped, one-line** — `\footnote{% CITE: <hint>}`; compile-unsafe (the `%` comments out the closing brace). Recognize it and recommend running writing-article-plans' `assemble_manuscript.py` first.

`% RESULT:` slots belong to a different pipeline and MUST never be touched or removed. The contract lives in the phase docs: Phase 1 enumerates slots into `citation_slots`, Phase 3a fills each or defers it to `unfilled_slots`, Phase 4 reports the tally, and Phase 5 executes the replacements and runs a deterministic `grep` closure check. See `references/phase-details-inline.md` and `references/phase-details-footnotes.md`.

## Inline Mode — Phase Overview (5 phases)

Detailed instructions: `references/phase-details-inline.md`.

- **Phase 1 — Manuscript Mapping.** Read the `.tex`; produce `placement/section_map.md` and `placement/existing_citations.json`. Detect the citation package (`natbib` → `\citet`/`\citep`; `biblatex` → `\textcite`/`\parencite`; else basic `\cite`) and the bibliography backend (`bibtex`/`biber`). **Cached** unless `replan` is `true`. Read-only. - **Phase 1.5 — Existing Citation Verification (optional).** Gated on `verify_citations`. Flags dangling `\cite{}` keys, hallucinated `.bib` entries, and spreadsheet overlaps into `placement/audit_report.json`. - **Phase 2 — Citation Ingestion.** `scripts/core/ingest_citations.py` turns the `.xlsx` into `citations.json` + `references_new.bib`. Deterministic, no LLM. - **Phase 3 — Placement Planning (3a → 3b → 3c).** 3a assigns each citation to all supporting sections (multi-placement is normal); 3b spawns one general-purpose sub-agent per section to draft anchors and cite commands, keyed to `insertion_style` (`prose` default — Types 1/2/3 with sentence rewriting; `simple` — parenthetical-only, no rewriting); 3c consolidates into `placement/placement_plan.md`. **Cached / incremental**: with `replan: false`, only cite keys absent from the `planned_keys` header trigger new planning. - **Phase 4 — HITL Review.** Always print the plan. Pause for corrections when `auto_approve` is `false`; otherwise continue immediately. - **Phase 5 — Execution.** Copy the `.tex` to a versioned output, insert cites (parenthetical = insert after anchor; prose/textual = replace anchor), merge `references_new.bib`, ensure `\bibliographystyle{}`/`\bibliography{}` (or `\addbibresource`/`\printbibliography` for `biblatex`), then compile with `pdflatex` + `bibtex`/`biber` + two more `pdflatex` passes.

## Footnote Mode — Phase Overview (6 phases)

Detailed instructions: `references/phase-details-footnotes.md`. Accepts `.tex` (LaTeX `\footnote{}`, compiled with `xelatex`) or `.docx` (native OOXML footnotes via `scripts/core/docx_support/`); for `.docx`, skip every LaTeX-specific step (no `xelatex`, no `%CITE-PLACED`, no `\bibliography{}`).

- **Phase 1 — Manuscript Mapping.** Produce `placement/section_map.md` and `placement/existing_footnotes.json`, classifying each footnote (`article`/`book`/`working_paper`/`case`/`legislation`/`cross_reference`/`discursive`/`mixed`). **Cached** unless `replan`. - **Phase 1.5 — Existing Citation Audit (optional).** Gated on `verify_citations`; verification cascade (OpenAlex → CrossRef → Google Scholar) into `placement/audit_report.json`. - **Phase 2 — Citation Ingestion.** `scripts/core/ingest_citations.py` → `citations.json` + `references_new.bib`. Deterministic. - **Phase 3 — Placement Planning (3a → 3b → 3c).** Style-specific rules are read from `references/styles/<citation_style>.md` and injected into the 3b sub-agent prompts; every placement carries the **full** citation string (Phase 6 handles repeats). 3c merges same-anchor placements into single multi-citation footnotes. **Cached / incremental** on the `planned_keys` header. - **Phase 4 — HITL Review.** Pause when `auto_approve` is `false`. - **Phase 5 — Execution.** Copy the manuscript; insert each `\footnote{` with an invisible `%CITE-PLACED` marker immediately after the opening brace; apply Phase 1.5 audit fixes; tag any pre-existing footnotes with `%CITE-PLACED`; run `merge_adjacent_footnotes.py`; then Phase 6; then `xelatex` (one pass, no `bibtex`/`biber`). - **Phase 6 — Short-Form Post-Processing.** `short_form.py` converts repeat citations to the style's short form (Id./ibid/supra/shortened title/author-date) and writes `placement/footnote_registry.json` for later cross-reference reordering. Runs automatically after Phase 5; compile `xelatex` twice to settle footnote numbers.

### `%CITE-PLACED` marker rule

Every `\footnote{}` in a `.tex` output carries `%CITE-PLACED` immediately after the opening brace (a LaTeX comment `pdflatex` ignores, so the PDF is unchanged). The marker lets `strip_citations.py` cleanly remove all pipeline footnotes for a clean re-run, and it is preserved through merge and short-form rewrites.

## Restyle Mode — Overview

Detailed instructions: Restyle Pipeline section of `references/phase-details-footnotes.md`. Converts every existing footnote citation from `current_style` to `target_style`, correcting Id./ibid/supra cross-references and symbol-footnote numbering. The `.tex` path spawns one sub-agent per section and finishes with `merge_adjacent_footnotes.py` + `short_form.py`; the `.docx` path extracts footnotes via `scripts/core/docx_support/`, restyles them, and writes back via `replace_footnote_text`. Standalone drivers: `scripts/docx_restyle.py` and `scripts/tex_restyle.py` (each takes `--config placement/run_config.json`). Case citations, legislation, and discursive footnotes pass through unchanged.

## Utilities

The launcher's Utilities area (and the corresponding scripts) support maintenance outside a full run:

- **Strip All Citations** — `strip_citations.py` removes every `%CITE-PLACED` footnote, yielding a clean manuscript for a from-scratch re-run. - **Regenerate / Reorder Cross-Refs** — `re

Technical details

Version
1.0.0
License
MIT
Last updated
Aug 24, 2026
Published
Aug 24, 2026

Decision snapshot

Fallback candidate

62
Ready
Prototype
Stage

recent repository activity

Audit

Install review

Install and adoption review

74
Needs review
Security
76/100
Maintenance
100/100
Install
92/100
Open full auditView eval report

Agent-proven evidence

Agent-proven evidence

Outcome reports after resolve, review, install, and one narrow run.

0
Proven
Needs first agent runAuto-install: review firstLast: Unknown
Success rate
Recent failure
Outcomes
0
Output quality
Failed
0
Not relevant
0
Installs
0
Risk blocked
0
Setup needed
0
Production
0

No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.

Install

Add to agent workflow

Free and open source. Review the report before installing into production agents.

Growth loop

Share kit

X

Scenario-led draft for cite-placement, ready for a manual X post.

Curator note
For a repeatable workflow, this is a skill worth shortlisting before another blank prompt.

cite-placement: >-

47 stars

https://www.openagentskill.com/skills/kennethkhoocy-cite-placement?ref=x
Open X draft
Optional reply with install command
Listing + install path for cite-placement:
https://www.openagentskill.com/skills/kennethkhoocy-cite-placement?ref=x

Install: npx skills add kennethkhoocy/applied-micro-skills --skill cite-placement

Listing source

Registry indexed

Claimable

This listing was indexed from public sources and is not marked official until a maintainer claim is approved.

Indexed by
OpenAgentSkill community index

Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.

Claim this skill

Owner claim

Claim this skill listing

This Registry indexed listing is attributed to kennethkhoocy but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.

Creator backlink kit

Add the evidence badges to your README

Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.

[![Listed on OpenAgentSkill](https://www.openagentskill.com/api/badge/kennethkhoocy-cite-placement?metric=listed&label=Listed)](https://www.openagentskill.com/skills/kennethkhoocy-cite-placement)
[![OpenAgentSkill Trust](https://www.openagentskill.com/api/badge/kennethkhoocy-cite-placement?metric=trust&label=Trust)](https://www.openagentskill.com/skills/kennethkhoocy-cite-placement)
[![OpenAgentSkill Audit](https://www.openagentskill.com/api/badge/kennethkhoocy-cite-placement?metric=audit&label=Audit)](https://www.openagentskill.com/skills/kennethkhoocy-cite-placement/audit)
[![Agent Proven](https://www.openagentskill.com/api/badge/kennethkhoocy-cite-placement?metric=proven&label=Agent%20Proven)](https://www.openagentskill.com/skills/kennethkhoocy-cite-placement)

Author

K

kennethkhoocy

@kennethkhoocy

Platform fit

Health signals

GitHub stars
47
Quality score
35/100
Last GitHub push
Aug 24, 2026
Framework hints
Unknown
OpenAgentSkill views
0
Install copies
0
Outbound clicks
0

Community signal

Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.

Trust & safety

Do not auto-install

57
  • GitHub adoption47 GitHub starsCHECK
  • Stars/forks activity47 stars, 0 forks; issue activity unavailable in current metadataCHECK
  • Recent maintenancePushed todayPASS
  • License clarityMITPASS
  • README/SKILL.md completenessPublic metadata needs stronger README/SKILL.md contextCHECK
  • Dependency/runtime riskcommand execution surfaceINFO