\r

Academic Citation Style Formatter and Converter\r

\r

When to Use\r

\r

• Use this skill when the task needs Use when formatting references for journal submission, converting between citation styles (APA, MLA, Vancouver, Chicago), generating bibliographies for manuscripts, or ensuring consistent reference formatting. Automatically formats citations and bibliographies in 1000+ academic styles. Ensures reference accuracy, completeness, and compliance with journal requirements. Supports batch conversion and integration with reference managers.\r
• Use this skill for academic writing tasks that require explicit assumptions, bounded scope, and a reproducible output format.\r
• Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.\r \r

Key Features\r

\r

• Scope-focused workflow aligned to: Use when formatting references for journal submission, converting between citation styles (APA, MLA, Vancouver, Chicago), generating bibliographies for manuscripts, or ensuring consistent reference formatting. Automatically formats citations and bibliographies in 1000+ academic styles. Ensures reference accuracy, completeness, and compliance with journal requirements. Supports batch conversion and integration with reference managers.\r
• Packaged executable path(s): scripts/main.py.\r
• Reference material available in references/ for task-specific guidance.\r
• Structured execution path designed to keep outputs consistent and reviewable.\r \r

Dependencies\r

\r

• Python: 3.10+. Repository baseline for current packaged skills.\r
• Third-party packages: not explicitly version-pinned in this skill package. Add pinned versions if this skill needs stricter environment control.\r \r

Example Usage\r

\r

cd "20260318/scientific-skills/Academic Writing/citation-formatter"\r
python -m py_compile scripts/main.py\r
python scripts/main.py --help\r
```\r
\r
Example run plan:\r
1. Confirm the user input, output path, and any required config values.\r
2. Edit the in-file `CONFIG` block or documented parameters if the script uses fixed settings.\r
3. Run `python scripts/main.py` with the validated inputs.\r
4. Review the generated output and return the final artifact with any assumptions called out.\r
\r
## Implementation Details\r
\r
See `## Workflow` above for related details.\r
\r
- Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.\r
- Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.\r
- Primary implementation surface: `scripts/main.py`.\r
- Reference guidance: `references/` contains supporting rules, prompts, or checklists.\r
- Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.\r
- Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.\r
\r
## Quick Check\r
\r
Use this command to verify that the packaged script entry point can be parsed before deeper execution.\r
\r
```bash\r
python -m py_compile scripts/main.py\r
```\r
\r
## Audit-Ready Commands\r
\r
Use these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.\r
\r
```bash\r
python -m py_compile scripts/main.py\r
python scripts/main.py --help\r
python scripts/main.py --input "Audit validation sample with explicit symptoms, history, assessment, and next-step plan." --format json\r
```\r
\r
## Workflow\r
\r
1. Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.\r
2. Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.\r
3. Use the packaged script path or the documented reasoning path with only the inputs that are actually available.\r
4. Return a structured result that separates assumptions, deliverables, risks, and unresolved items.\r
5. If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.\r
\r
## When to Use This Skill\r
\r
- formatting references for journal submission\r
- converting between citation styles (APA, MLA, Vancouver, Chicago)\r
- generating bibliographies for manuscripts\r
- ensuring consistent reference formatting\r
- checking reference completeness and accuracy\r
- preparing grant proposal reference sections\r
\r
## Quick Start\r
\r
```python\r
from scripts.main import CitationFormatter\r
\r
# Initialize the tool\r
tool = CitationFormatter()\r
\r
from scripts.citation_formatter import CitationFormatter\r
\r
formatter = CitationFormatter()\r
\r
# Format references for specific journal\r
formatted_refs = formatter.format_references(\r
    references=raw_references,\r
    target_style="Nature Medicine",\r
    output_format="docx"\r
)\r
\r
# Convert between styles\r
converted = formatter.convert_style(\r
    bibliography=apa_bibliography,\r
    from_style="APA 7th",\r
    to_style="Vancouver",\r
    include_doi=True,\r
    include_pmids=True\r
)\r
\r
# Validate reference completeness\r
validation = formatter.validate_references(\r
    references=reference_list,\r
    required_fields=["authors", "title", "journal", "year", "volume", "pages", "doi"]\r
)\r
\r
print(f"Validation results:")\r
print(f"  Complete: {validation.complete_count}")\r
print(f"  Missing fields: {validation.incomplete_count}")\r
print(f"  Invalid DOIs: {len(validation.invalid_dois)}")\r
\r
# Generate in-text citations\r
in_text = formatter.generate_in_text_citations(\r
    citations=[\r
        {"author": "Smith", "year": 2023, "type": "paren"},\r
        {"author": "Jones et al.", "year": 2022, "type": "narrative"}\r
    ],\r
    style="APA"\r
)\r
\r
# Batch process multiple documents\r
batch_results = formatter.batch_format(\r
    files=["chapter1.docx", "chapter2.docx"],\r
    style="AMA",\r
    output_dir="formatted/"\r
)\r
```\r
\r
## Core Capabilities\r
\r
### 1. Format citations in 1000+ academic styles\r
\r
```python\r
\r
# Format functionality\r
result = tool.execute(data)\r
```\r
\r
### 2. Convert seamlessly between citation formats\r
\r
```python\r
\r
# Convert functionality\r
result = tool.execute(data)\r
```\r
\r
### 3. Validate reference completeness and accuracy\r
\r
```python\r
\r
# Validate functionality\r
result = tool.execute(data)\r
```\r
\r
### 4. Batch process large reference collections\r
\r
```python\r
\r
# Batch functionality\r
result = tool.execute(data)\r
```\r
\r
## Command Line Usage\r
\r
```text\r
python scripts/main.py --input references.bib --from-style APA --to-style Vancouver --output formatted.docx --validate\r
```\r
\r
## Best Practices\r
\r
- Always validate DOIs and URLs before submission\r
- Check journal-specific requirements beyond standard style\r
- Maintain original reference database for updates\r
- Review formatting of special cases (websites, preprints)\r
\r
## Quality Checklist\r
\r
Before using this skill, ensure you have:\r
- [ ] Clear understanding of your objectives\r
- [ ] Necessary input data prepared and validated\r
- [ ] Output requirements defined\r
- [ ] Reviewed relevant documentation\r
\r
After using this skill, verify:\r
- [ ] Results meet your quality standards\r
- [ ] Outputs are properly formatted\r
- [ ] Any errors or warnings have been addressed\r
- [ ] Results are documented appropriately\r
\r
## References\r
\r
- `references/guide.md` - Comprehensive user guide\r
- `references/examples/` - Working code examples\r
- `references/api-docs/` - Complete API documentation\r
\r
---\r
\r
**Skill ID**: 625 | **Version**: 1.0 | **License**: MIT\r
\r
## Output Requirements\r
\r
Every final response should make these items explicit when they are relevant:\r
\r
- Objective or requested deliverable\r
- Inputs used and assumptions introduced\r
- Workflow or decision path\r
- Core result, recommendation, or artifact\r
- Constraints, risks, caveats, or validation needs\r
- Unresolved items and next-step checks\r
\r
## Error Handling\r
\r
- If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.\r
- If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.\r
- If `scripts/main.py` fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.\r
- Do not fabricate files, citations, data, search results, or execution outcomes.\r
\r
## Input Validation\r
\r
This skill accepts requests that match the documented purpose of `citation-formatter` and include enough context to complete the workflow safely.\r
\r
Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:\r
\r
> `citation-formatter` only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.\r
\r
## Response Template\r
\r
Use the following fixed structure for non-trivial requests:\r
\r
1. Objective\r
2. Inputs Received\r
3. Assumptions\r
4. Workflow\r
5. Deliverable\r
6. Risks and Limits\r
7. Next Checks\r
\r
If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.\r