@lylll9436/paper-polish-workflow-skill 2.1.0

package/.claude/skills/ppw-experiment/SKILL.md

@@ -0,0 +1,290 @@
+---
+name: ppw:experiment
+description: >-
+  Analyze experiment results and generate discussion paragraphs for academic papers.
+  Two-phase workflow: identify measurable findings (Phase 1), confirm with user,
+  then generate grounded discussion paragraphs (Phase 2).
+  Accepts tables, statistics, or result descriptions. 实验分析与讨论段落生成。
+triggers:
+  primary_intent: analyze experiment results and generate discussion paragraphs
+  examples:
+    - "Analyze my experiment results"
+    - "帮我分析实验结果"
+    - "Generate discussion for my results table"
+    - "把我的实验数据写成讨论段"
+    - "Write discussion paragraphs for my findings"
+    - "帮我写实验讨论部分"
+    - "Identify patterns in my experiment data"
+tools:
+  - Read
+  - Write
+  - Structured Interaction
+references:
+  required:
+    - references/expression-patterns.md
+    - references/bilingual-output.md
+  leaf_hints:
+    - references/expression-patterns/results-and-discussion.md
+    - references/expression-patterns/conclusions-and-claims.md
+    - references/expression-patterns/methods-and-data.md
+    - references/anti-ai-patterns/vocabulary.md
+input_modes:
+  - file
+  - pasted_text
+  - structured_data
+output_contract:
+  - pattern_analysis
+  - discussion_paragraphs
+  - bilingual_discussion
+---
+
+## Purpose
+
+This Skill accepts experiment result data — tables, statistics, or result descriptions —
+and runs a two-phase workflow. Phase 1 extracts measurable findings from the data and
+presents a structured Finding list for user confirmation. Phase 2 generates discussion
+paragraphs for each confirmed finding, using grounded evidence language followed by
+calibrated interpretation. Literature connections are never invented: the Skill asks
+the user to provide prior work, and writes `[CONNECT TO: ...]` placeholders when none
+is supplied. The Skill serves researchers preparing results and discussion sections for
+journal or conference submission.
+
+## Core Prompt
+
+> Source: [awesome-ai-research-writing](https://github.com/Leey21/awesome-ai-research-writing) — 实验分析
+
+````markdown
+# Role
+你是一位具有敏锐洞察力的资深数据科学家，擅长处理复杂的实验数据并撰写高质量的学术分析报告。
+
+# Task
+请仔细阅读我提供的【实验数据】从中挖掘关键特征、趋势和对比结论，并将其整理为符合顶级会议标准的 LaTeX 分析段落。
+
+# Constraints
+1. 数据真实性：
+   - 所有结论必须严格基于输入的数据。严禁编造数据、夸大提升幅度或捏造不存在的实验现象。
+   - 如果数据中没有明显的优势或趋势，请如实描述，不要强行总结所谓的显著提升。
+
+2. 分析深度：
+   - 拒绝简单的报账式描述（例如不要只说 A 是 0.5，B 是 0.6），重点在于比较和趋势分析。
+   - 关注点包括：方法的有效性（SOTA 比较）、参数的敏感性、性能与效率的权衡，以及消融实验中的关键模块贡献。
+
+3. 排版与格式规范：
+   - 严禁使用加粗或斜体：正文中不要使用 \textbf 或 \emph，依靠文字逻辑来表达重点。
+   - 结构强制：必须使用 \paragraph{核心结论} + 分析文本 的形式。
+     * \paragraph{} 中填写高度凝练的短语结论（使用 Title Case 格式）。
+     * 紧接着在同一段落中展开具体的数值分析和逻辑推演。
+   - 不要使用列表环境，保持纯文本段落。
+
+4. 输出格式：
+   - Part 1 [LaTeX]：只输出分析后的 LaTeX 代码。
+     * 必须对特殊字符进行转义（例如：`%`、`_`、`&`）。
+     * 保持数学公式原样（保留 `$` 符号）。
+     * 不同的结论点之间请空一行。
+   - Part 2 [Translation]：对应的中文直译（用于核对数据结论是否准确）。
+   - 除以上两部分外，不要输出任何多余的对话。
+````
+
+## Trigger
+
+**Activates when the user asks to:**
+- Analyze experiment results, identify patterns, or extract findings from result data
+- Generate discussion paragraphs from confirmed findings
+- 分析实验结果、识别规律、生成讨论段落
+
+**Example invocations:**
+- "Analyze my results table and write discussion"
+- "帮我分析实验结果并写讨论段"
+- "Generate discussion paragraphs for my findings"
+- "What patterns do my experiment results show?"
+
+## Modes
+
+| Mode | Default | Behavior |
+|------|---------|----------|
+| `direct` | Yes | Full two-phase workflow: Phase 1 finding list → user confirm → Phase 2 discussion |
+| `batch` | | Not supported — experiment analysis requires full context of the complete results set |
+
+**Default mode:** `direct`. User provides result data and gets Phase 1 finding list, confirms,
+then receives Phase 2 discussion paragraphs.
+
+**Mode inference:** "Just identify findings" or "只分析不写讨论" runs Phase 1 only.
+
+## References
+
+### Required (always loaded)
+
+| File | Purpose |
+|------|---------|
+| `references/expression-patterns.md` | Expression patterns overview; loaded at Phase 1 start |
+
+### Leaf Hints (loaded in Phase 2)
+
+| File | When to Load |
+|------|--------------|
+| `references/expression-patterns/results-and-discussion.md` | Always in Phase 2 — result reporting and pattern interpretation language |
+| `references/expression-patterns/conclusions-and-claims.md` | Always in Phase 2 — calibrated claim language (suggests, indicates, scope) |
+| `references/expression-patterns/methods-and-data.md` | In Phase 2 if user's result description includes method details needing clarification |
+| `references/anti-ai-patterns/vocabulary.md` | In Phase 2 — screen generated output for AI-sounding vocabulary |
+
+### Conditional
+
+| File | When to Load |
+|------|--------------|
+| `references/journals/[journal].md` | When user specifies a target journal. If missing, **refuse**: "Journal template for [X] not found. Available: CEUS." |
+
+## Ask Strategy
+
+**Before starting, ask about:**
+1. Research questions: "What are the main research questions this experiment addresses?"
+   (Required — Phase 2 uses these to connect findings to purpose)
+2. Prior work to connect to: "Which papers or findings should the discussion reference?"
+   (Optional — ask once; if declined, use `[CONNECT TO: ...]` placeholders in Phase 2)
+3. Target journal (if not specified): ask once; if declined, use general academic style
+
+**Rules:**
+- Never ask more than 3 questions before starting Phase 1
+- Research questions are mandatory; the Skill cannot produce grounded Phase 2 output without them
+- If the user declines to provide research questions, write `[RESEARCH QUESTION: describe your RQ here]`
+  placeholders rather than blocking the workflow entirely
+
+## Workflow
+
+### Step 0: Workflow Memory Check
+
+- Read `.planning/workflow-memory.json`. If file missing or empty, skip to Phase 1.
+- Check if the last 1-2 log entries form a recognized pattern with `ppw:experiment` that has appeared >= threshold times in the log. See `skill-conventions.md > Workflow Memory > Pattern Detection` for the full algorithm.
+- If a pattern is found, present recommendation via AskUserQuestion:
+  - Question: "检测到常用流程：[pattern]（已出现 N 次）。是否直接以 direct 模式运行 ppw:experiment？"
+  - Options: "Yes, proceed" / "No, continue normally"
+- If user accepts: set mode to `direct`, skip Ask Strategy questions.
+- If user declines or AskUserQuestion unavailable: continue in normal mode.
+
+### Phase 1: Analyze Results
+
+**Step 1 — Prepare:**
+- Load `references/expression-patterns.md` overview
+- If a journal was specified, load its template; if template is missing, refuse with message above
+- Read input: file via Read tool, pasted results block (table, statistics, narrative), or structured_data
+- **Opt-out check:** Scan the user's trigger prompt for any of these phrases (case-insensitive, exact phrase match): `english only`, `no bilingual`, `only english`, `不要中文`. Store result as `bilingual_mode` (true/false). This flag governs Phase 2 bilingual output below.
+- **Guard — measurable data required:** if input is vague (e.g., "my results show improvement"
+  without values, comparisons, or metrics), refuse: "Please provide specific values, comparisons,
+  or metrics before I can identify findings."
+- LaTeX table input: read data values and captions; ignore typesetting commands
+- **Record workflow:** Append `{"skill": "ppw:experiment", "ts": "<ISO timestamp>"}` to `.planning/workflow-memory.json`. Create file as `[]` if missing. Drop oldest entry if log length >= 50.
+
+**Step 2 — Extract Findings:**
+- Identify measurable comparisons: method A vs. method B, magnitude, direction
+- Identify trends: performance across conditions, dataset sizes, subgroups
+- Identify outliers: results that deviate from the overall pattern
+- Each finding must include: a direction (higher/lower/better/worse), a magnitude or value,
+  and a comparison group or condition
+
+**Step 3 — Present Finding List:**
+- Use locked format per item:
+  ```
+  Finding 1: [subject] [comparison/trend] [value] on [metric/condition]
+  Finding 2: Performance degrades in [condition] ([N] vs. [M])
+  Finding 3: [Subgroup] shows the largest effect ([value])
+  ```
+- Summary line: "Identified N findings. Please confirm, correct, or add before I write discussion."
+- Wait for user approval before proceeding to Phase 2
+
+---
+
+### Phase 2: Generate Discussion
+
+**Step 1 — Prepare:**
+- Load `references/expression-patterns/results-and-discussion.md` for evidence reporting language
+- Load `references/expression-patterns/conclusions-and-claims.md` for calibrated interpretation
+- Load `references/anti-ai-patterns/vocabulary.md` to screen output before presenting
+- Hold any user-provided prior work for connection sentences
+
+**Step 2 — Write Discussion Paragraphs:**
+- **Follow the Core Prompt constraints above** as the primary instruction set for analysis and output formatting.
+- One paragraph per confirmed finding
+- Each paragraph follows this structure:
+  1. **Evidence sentence:** state the finding with full quantification
+     (use results-and-discussion.md patterns for comparative and trend language)
+  2. **Interpretation sentence:** claim using calibrated language from conclusions-and-claims.md
+     ("suggests", "indicates" — never lead with interpretation before evidence)
+  3. **Connection sentence:** if user provided prior work, connect the finding to it;
+     otherwise write `[CONNECT TO: describe the prior finding here]`
+- **CRITICAL rule:** Interpretation sentence must follow the evidence sentence. Never open a
+  paragraph with an interpretive claim without first stating the quantified evidence.
+- After generating all paragraphs, check output against vocabulary.md; revise any flagged patterns
+
+**Step 3 — Output:**
+- Present all discussion paragraphs in sequence
+- **Bilingual display:** If `bilingual_mode` is true: after each discussion paragraph, append a `> **[Chinese]** ...` blockquote containing the Chinese translation of that paragraph. Use a section header "**双语对照 / Bilingual Comparison:**" before the first paragraph. Format per finding paragraph:
+
+  [English discussion paragraph for Finding N]
+
+  > **[Chinese]** [Chinese translation of the discussion paragraph for Finding N]
+
+- Do not insert Chinese into any written file. If the user requested writing discussion to the paper file via Write tool, write English-only paragraphs to the file; the Chinese blockquotes remain in conversation only.
+- If `bilingual_mode` is false (opt-out detected): skip bilingual display entirely.
+- If file input was used, offer to append discussion to file using Write tool
+- Recommend Polish Skill for further expression refinement if higher-register prose is desired
+
+## Output Contract
+
+| Output | Format | Condition |
+|--------|--------|-----------|
+| `pattern_analysis` | Structured Finding list (Finding N: format) | Always — Phase 1 |
+| `discussion_paragraphs` | One paragraph per confirmed finding | Phase 2 only, after Phase 1 confirmation |
+| `bilingual_discussion` | `> **[Chinese]** ...` blockquotes in session (one per finding paragraph) | Phase 2 only. Skipped when opt-out detected. Not written to file. |
+
+**Note:** Phase 2 output cannot be produced without Phase 1 confirmation. If user skips Phase 1
+and requests discussion directly, require Phase 1 completion first.
+
+## Edge Cases
+
+| Situation | Handling |
+|-----------|----------|
+| Input is vague (no measurable values) | Refuse Phase 1 with: "Please provide specific values, comparisons, or metrics before I can identify findings." |
+| User skips Phase 1 and asks for discussion | Require Phase 1 completion first; do not generate paragraphs without confirmed findings |
+| User provides no research questions | Ask once; if declined, write `[RESEARCH QUESTION: describe your RQ here]` placeholders |
+| User provides no prior literature | Use `[CONNECT TO: ...]` placeholders; do not attempt to name papers or authors |
+| Only one finding identified | Produce a single discussion paragraph; do not pad or invent additional findings |
+| Finding conflicts with user-stated hypothesis | Flag the discrepancy explicitly; do not suppress the conflicting result |
+| Journal specified but template missing | Refuse: "Journal template for [X] not found. Available: CEUS." |
+| Input is LaTeX table markup | Read data values and captions; ignore typesetting commands |
+| Phase 1 produces no findings | Report "No measurable findings identified from input" and stop |
+
+## Fallbacks
+
+| Scenario | Fallback |
+|----------|----------|
+| Structured Interaction unavailable | Ask 1-3 plain-text questions: research questions, prior work, target journal |
+| Expression pattern leaf missing | Proceed with general academic register; warn user of reduced quality |
+| Write tool fails | Present discussion paragraphs in conversation; user saves manually |
+| Phase 1 produces no findings | Report clearly and stop; do not proceed to Phase 2 |
+
+## Examples
+
+**Minimal invocation:** User pastes a results table comparing Method A and Method B on accuracy
+and F1 score. User states RQ: "Does our approach outperform the baseline on both metrics?"
+
+**Phase 1 output:**
+```
+Finding 1: Method A outperforms Method B by 3.2 percentage points on accuracy (87.4% vs. 84.2%)
+Finding 2: Method A outperforms Method B by 4.1 points on F1 score (82.6 vs. 78.5)
+
+Identified 2 findings. Please confirm, correct, or add before I write discussion.
+```
+
+**User confirms.** No prior work provided.
+
+**Phase 2 output (Finding 1):**
+```
+Method A achieves 87.4% accuracy, outperforming Method B by 3.2 percentage points (84.2%).
+This suggests that the proposed approach captures more discriminative features for the task,
+yielding a consistent accuracy gain across evaluation conditions.
+[CONNECT TO: describe a prior finding showing similar accuracy improvements for this approach]
+```
+
+---
+
+*Skill: experiment-skill*
+*Conventions: references/skill-conventions.md*

package/.claude/skills/ppw-literature/SKILL.md

@@ -0,0 +1,237 @@
+---
+name: ppw:literature
+description: >-
+  Search academic literature via Semantic Scholar MCP, select papers interactively,
+  and generate verified BibTeX entries. 文献检索与BibTeX生成，通过Semantic Scholar MCP。
+triggers:
+  primary_intent: search academic literature and generate BibTeX citations
+  examples:
+    - "Find papers about urban heat island"
+    - "帮我找关于城市热岛的文献"
+    - "Search literature for spatiotemporal analysis"
+    - "生成这篇文章的BibTeX引用"
+    - "Find relevant papers on deep learning for land use classification"
+    - "帮我检索相关文献并生成引用格式"
+tools:
+  - External MCP
+  - Structured Interaction
+references:
+  required: []
+  leaf_hints: []
+input_modes:
+  - pasted_text
+output_contract:
+  - bibtex_entry
+---
+
+## Purpose
+
+This Skill searches academic literature using the Semantic Scholar MCP, presents an interactive numbered result list (up to 10 papers), waits for the user to select a specific paper, then generates a verified BibTeX entry built exclusively from MCP-returned data. Before any workflow begins, a pre-flight probe confirms MCP availability — if unavailable, the Skill refuses immediately with setup instructions rather than proceeding with degraded capability. After the user selects a paper, a mandatory anti-hallucination verification prompt reminds the user to confirm the paper's actual relevance before committing the citation. This Skill does not write or rewrite paper content; it searches, selects, and generates citation entries only.
+
+## Trigger
+
+**Activates when the user asks to:**
+- Search or find academic papers on a topic
+- Generate BibTeX or citation entries for a reference
+- 帮我找文献、检索相关论文、帮我生成引用格式
+
+**Example invocations:**
+- "Find papers about urban heat island" / "帮我找关于城市热岛的文献"
+- "Search literature for spatiotemporal analysis" / "检索时空分析相关文献"
+- "Generate BibTeX for a citation" / "帮我生成BibTeX引用格式"
+
+## Modes
+
+| Mode | Default | Behavior |
+|------|---------|----------|
+| `direct` | Yes | Single-shot search → result list → user selects → BibTeX generated; no iteration |
+| `batch` | | Not supported — each search requires user selection in session |
+
+**Default mode:** `direct`. Search is single-shot: if results are unsatisfactory, user re-triggers the Skill with different keywords.
+
+## References
+
+### Required (always loaded)
+
+None. This is a search task — no expression pattern files needed.
+
+### Leaf Hints
+
+None.
+
+> No reference files loaded. All paper metadata sourced from Semantic Scholar MCP at runtime.
+
+## Ask Strategy
+
+The Skill collects search inputs conversationally. At most two questions:
+
+1. **Search query** (required): the topic or keyword to search — ask only if not provided in the trigger message.
+2. **Result count** (optional): how many results to display. Default: 5. Maximum: 10.
+
+If the user provides the topic in the trigger message, skip question 1 and proceed immediately.
+
+## Workflow
+
+### Step 0: Workflow Memory Check
+
+- Read `.planning/workflow-memory.json`. If file missing or empty, skip to Step 1.
+- Check if the last 1-2 log entries form a recognized pattern with `ppw:literature` that has appeared >= threshold times in the log. See `skill-conventions.md > Workflow Memory > Pattern Detection` for the full algorithm.
+- If a pattern is found, present recommendation via AskUserQuestion:
+  - Question: "检测到常用流程：[pattern]（已出现 N 次）。是否直接以 direct 模式运行 ppw:literature？"
+  - Options: "Yes, proceed" / "No, continue normally"
+- If user accepts: set mode to `direct`, skip Ask Strategy questions.
+- If user declines or AskUserQuestion unavailable: continue in normal mode.
+
+### Step 1: MCP Pre-flight Check
+
+1. Call `mcp__semantic-scholar__papers-search-basic` with `{"query": "test", "limit": 1}`.
+2. If the call succeeds: proceed to Step 2.
+3. If the call fails or tool is unavailable: **refuse immediately** with:
+
+   > "Semantic Scholar MCP is not available. To use this Skill:
+   > 1. Open Claude Code Settings → MCP Servers
+   > 2. Add the Semantic Scholar server (server key: `semanticscholar`)
+   > 3. Restart Claude Code and retry"
+
+   Do NOT proceed past this point if MCP is unavailable.
+
+### Step 2: Collect Search Query
+
+1. Extract the search topic from the trigger message if present.
+2. If topic not provided, ask: "What topic or keywords should I search for?"
+3. Confirm result count (default: 5).
+- **Record workflow:** Append `{"skill": "ppw:literature", "ts": "<ISO timestamp>"}` to `.planning/workflow-memory.json`. Create file as `[]` if missing. Drop oldest entry if log length >= 50.
+
+### Step 3: Execute Search and Build Result Cards
+
+1. Call `mcp__semantic-scholar__papers-search-basic` with the user's query and result count.
+2. For each returned paper: if the abstract field is empty in the search result, call `mcp__semantic-scholar__get-paper-abstract` to fetch an abstract excerpt.
+3. Display numbered result cards in this exact format:
+
+   ```
+   **[1] Title of the Paper**
+   Authors: Smith, J.; Lee, K. · Year: 2023 · Citations: 142
+   > "One sentence from abstract describing the core contribution..."
+
+   **[2] Another Relevant Paper**
+   Authors: Zhang, W. · Year: 2022 · Citations: 89
+   > "Abstract not available"
+   ```
+
+4. End the display with: "Please select a paper (enter number), or type 'none' to cancel."
+
+### Step 4: User Selection
+
+1. Wait for the user to enter a number or "none".
+2. If "none": respond "Search cancelled." and end the session.
+3. If out-of-range number: ask the user to re-enter a valid number from the displayed list.
+4. If valid number: confirm the selection by restating the paper title.
+5. Display the **mandatory verification prompt** (never omit):
+
+   > "Please confirm that the selected paper actually supports the claim you are citing — do not rely solely on the title."
+
+### Step 5: Generate BibTeX
+
+1. Construct the BibTeX entry using **only fields returned by the MCP** for the selected paper.
+2. Citation key format: `firstAuthorLastnameLowercaseYYYYfirstKeyword` (e.g., `smith2023urban`).
+3. Use `@article` for journal papers, `@inproceedings` for conference papers, `@misc` for preprints — follow the paper type returned by MCP.
+4. If any field (volume, pages, DOI) is not returned by MCP, **omit that field** — never fill from prior knowledge.
+5. Display the BibTeX in a code fence:
+
+   ````bibtex
+   @article{smith2023urban,
+     title     = {Full title from MCP},
+     author    = {Last, First and Last2, First2},
+     journal   = {Journal name from MCP},
+     year      = {2023},
+     volume    = {101},
+     pages     = {101943},
+     doi       = {10.1016/j.compenvurbsys.2023.101943}
+   }
+   ````
+
+## Output Contract
+
+| Output | Format | Condition |
+|--------|--------|-----------|
+| `bibtex_entry` | BibTeX code block (`@article`, `@inproceedings`, or `@misc`) | After user selects a paper |
+
+> All field values must come from the MCP-returned paper record. Never supply missing fields from prior knowledge — omit them instead.
+
+**Example BibTeX (all fields from MCP data):**
+
+```bibtex
+@article{li2022spatiotemporal,
+  title  = {Spatiotemporal Analysis of Urban Land Use Change},
+  author = {Li, Wei and Wang, Fang},
+  journal = {Computers, Environment and Urban Systems},
+  year   = {2022},
+  volume = {95},
+  pages  = {101812},
+  doi    = {10.1016/j.compenvurbsys.2022.101812}
+}
+```
+
+## Edge Cases
+
+| Situation | Handling |
+|-----------|----------|
+| MCP pre-flight fails | Refuse with exact setup instructions from Step 1; never proceed to search |
+| Search returns zero results | "No papers found for '[query]'. Try broader keywords or re-trigger with different terms." |
+| Abstract field missing for a result | Show "Abstract not available" in result card; do not skip the paper |
+| User selects out-of-range number | Ask to re-enter a valid number from the displayed list |
+| User types "none" | "Search cancelled." — end session |
+| MCP returns non-article type | Use `@inproceedings` or `@misc` as appropriate; never force `@article` |
+| DOI not returned by MCP | Omit `doi` field; add comment: `% DOI not available — please verify manually` |
+
+## Fallbacks
+
+| Scenario | Fallback |
+|----------|----------|
+| Semantic Scholar MCP unavailable | Refuse immediately with setup guidance (Step 1 handles this); no partial fallback mode |
+| `get-paper-abstract` call fails for one paper | Mark abstract as "Abstract not available"; continue displaying remaining results |
+| Structured Interaction unavailable | Ask search query as plain-text question; proceed with numbered list in conversation |
+| Basic search returns poor results | Inform user: "If results are poor, re-trigger the Skill with more specific keywords" (single-shot only) |
+
+## Examples
+
+**User:** "Find papers about urban heat island mitigation"
+
+**Skill:** [Pre-flight check passes silently] → Calls `mcp__semantic-scholar__papers-search-basic` with `{"query": "urban heat island mitigation", "limit": 5}` → Displays results:
+
+```
+**[1] Urban Heat Island Mitigation through Green Infrastructure**
+Authors: Smith, J.; Lee, K. · Year: 2023 · Citations: 142
+> "This study evaluates green roof and tree-planting strategies for reducing UHI intensity in dense urban cores."
+
+**[2] Cool Pavements and Their Effect on Urban Thermal Comfort**
+Authors: Zhang, W.; Chen, L. · Year: 2022 · Citations: 89
+> "A field experiment comparing reflective pavement materials across five climate zones."
+```
+
+Please select a paper (enter number), or type "none" to cancel.
+
+**User:** "1"
+
+**Skill:** "You selected: Urban Heat Island Mitigation through Green Infrastructure (Smith, J.; Lee, K., 2023)."
+
+> "Please confirm that the selected paper actually supports the claim you are citing — do not rely solely on the title."
+
+**Skill (after user confirms):**
+
+```bibtex
+@article{smith2023urban,
+  title   = {Urban Heat Island Mitigation through Green Infrastructure},
+  author  = {Smith, John and Lee, Kwang-Ho},
+  journal = {Computers, Environment and Urban Systems},
+  year    = {2023},
+  volume  = {101},
+  pages   = {101943},
+  doi     = {10.1016/j.compenvurbsys.2023.101943}
+}
+```
+
+---
+
+*Skill: literature-skill*
+*Conventions: references/skill-conventions.md*