feat: Agent Skill

[Claude]

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Create an Agent Skill</issue_title>
<issue_description>Create an Agent Skill under the skill directory. The agent is encouraged to use uvx wenxian to run wenxian (uv needs to be installed).</issue_description>

Comments on the Issue (you are @claude[agent] in this section)

• Fixes Create an Agent Skill #90

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.10%. Comparing base (8172ac1) to head (f3a0863).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #91   +/-   ##
=======================================
  Coverage   87.10%   87.10%           
=======================================
  Files          12       12           
  Lines         504      504           
=======================================
  Hits          439      439           
  Misses         65       65           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

This pull request implements an Agent Skill for wenxian, enabling AI assistants and IDEs to use wenxian for generating citations. The PR adds comprehensive documentation following the Agent Skills specification format and updates the main README to inform users about this new integration capability.

Changes:

• Added Agent Skill documentation (skill/SKILL.md) with comprehensive usage instructions, examples, and integration guidance
• Updated README.md to introduce the Agent Skill feature and provide installation instructions

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
skill/SKILL.md	New comprehensive Agent Skill documentation with YAML frontmatter, installation instructions, usage examples for all identifier types and output formats, troubleshooting guidance, and integration examples
README.md	Added new section documenting the Agent Skill feature, including links to supported platforms and usage example

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Inconsistent quoting of DOI identifier. Line 131 uses quotes around the DOI "10.1038/nature12373", but the "Using DOI" example at line 49 shows DOI identifiers without quotes. For consistency with line 49 and the guidance at line 72 (quotes are for titles with spaces), consider removing quotes from this DOI identifier.

Suggested change

	uvx wenxian from "10.1038/nature12373" >> references.bib
	uvx wenxian from 10.1038/nature12373 >> references.bib

[Copilot]

Incomplete documentation of output formats. The text only mentions -t text option but wenxian also supports -t markdown format (as shown in skill/SKILL.md and confirmed in the source code wenxian/main.py). Consider mentioning all available formats: bibtex (default), text, and markdown, or at least indicate that other formats are available.

Suggested change

	By default, `wenxian` outputs ${\mathrm{B{\scriptstyle{IB}} T_{\displaystyle E} X}}$ format. You can use the `-t text` or `--type text` option to generate plain text format.
	By default, `wenxian` outputs ${\mathrm{B{\scriptstyle{IB}} T_{\displaystyle E} X}}$ format. You can use the `-t text` or `--type text` option to generate plain text format, or `-t markdown` / `--type markdown` to generate Markdown format.

[Copilot]

Inconsistent quoting of DOI identifiers. Lines 119, 125, 126, 131, and 183 use quotes around DOI identifiers (e.g., "10.1038/nature12373"), but lines 49 and 171 show DOI identifiers without quotes. According to line 72, quotes are only required for paper titles with spaces. For consistency with the "Using DOI" example at line 49 and the guidance at line 72, consider removing quotes from DOI identifiers in these examples, or add a note explaining when quotes are needed.

Suggested change

	uvx wenxian from "10.1038/nature12373"
	```
	2. **Multiple citations**: Generate entries for multiple papers by running the command multiple times
	```bash
	uvx wenxian from "10.1038/nature12373"
	uvx wenxian from "10.1126/science.1158899"
	```
	3. **Save to file**: Redirect output to a .bib file
	```bash
	uvx wenxian from "10.1038/nature12373" >> references.bib
	uvx wenxian from 10.1038/nature12373

2. Multiple citations: Generate entries for multiple papers by running the command multiple times

   uvx wenxian from 10.1038/nature12373
   uvx wenxian from 10.1126/science.1158899

3. Save to file: Redirect output to a .bib file

   uvx wenxian from 10.1038/nature12373 >> references.bib

[Copilot]

Inconsistent quoting of identifiers. Lines 183-184 use quotes around DOI and arXiv identifiers in the batch processing example, but earlier examples consistently show these numeric identifiers without quotes (lines 49, 55, 81). For consistency with the rest of the documentation and the guidance at line 72 (quotes are for titles with spaces), consider removing quotes from these identifiers.

Suggested change

	uvx wenxian from "10.1038/nature12373" >> references.bib
	uvx wenxian from "1512.03385" >> references.bib
	uvx wenxian from 10.1038/nature12373 >> references.bib
	uvx wenxian from 1512.03385 >> references.bib