classify-temp-entries-to-section

$npx mdskill add kimtth/azure-openai-llm-wiki/classify-temp-entries-to-section

Classifies entries in temp_entries.md into corresponding section files

  • Identifies and categorizes new entries based on their titles to correct sections.
  • Depends on the structure of markdown files for classification decisions.
  • Decides by matching entry titles with existing section headings or content blocks.
  • Delivers classified entries directly into the appropriate section files.

SKILL.md

.github/skills/classify-temp-entries-to-sectionView on GitHub ↗
---
name: classify-temp-entries-to-section
description: "Classification guidelines for entries in temp_entries.md. Each entry have its own title with the markdown file name and section name in temp_entries.md. USE FOR: Classifying new entries in temp_entries.md into *.md in the section files. DO NOT USE FOR: 1) Adding new entries to temp_entries.md; 2) Moving entries between sections."
---

## Workflow: Classifying Entries in temp_entries.md

`temp_entries.md` is the staging file where new entries from `temp.md` are formatted before being inserted into the section files. Each entry in `temp_entries.md` should have a title indicating the target markdown file and section name for clarity.

**Steps for classification:**

1. **Identify the target section** — Based on the title of each entry, determine which markdown file under `section/` it belongs to and use the exact current heading from that file's `Contents` block or heading text.
2. **Insert into sections** — Once classified, entries should be moved from `temp_entries.md` to the appropriate section files (`azure.md`, `applications.md`, `models_research.md`, `best_practices.md`, `tools_extra.md`) under the correct live section headings.
3. **Maintain organization** — Ensure that entries are placed in the correct order within each section, following any existing formatting and structure. The entry are ordered by alphabetical order of the entry name under each section.
4. **Update temp_entries.md** — After classification and insertion, add Check emoji ✅ to the entry in `temp_entries.md` to keep it clean and track which entries have been processed.

Do not classify hand-curated entries into generated index files such as `section/x_llm_apps.md`, `section/x_llm_papers.md`, or `section/x_popular_papers.md`. Use the generator-specific skills for those files.

More from kimtth/azure-openai-llm-wiki

SkillDescription
add-new-entryWorkflow and tools for adding new entries from temp.md to the section files. Includes legend format, section reference, code tools, and common pitfalls. USE FOR: Adding new resources to the knowledge base. DO NOT USE FOR: Editing existing entries or restructuring sections.
update-app-countWorkflow for updating the popular LLM applications pool (section/x_llm_apps.md) using get_app_list_by_github_star.py. Covers full refresh, alternate exports, topic tuning, and common pitfalls. USE FOR: Refreshing the ranked GitHub applications list linked from applications.md. DO NOT USE FOR: Hand-curating application entries inside applications.md or adding GitHub star badges to the generated file.
update-cite-countGuidelines for updating citation counts for papers in the section files using the `update_citation_counts.py` tool. USE FOR: Updating citation counts for papers listed in the section files to keep information current. DO NOT USE FOR: 1) Adding new papers to the section files; 2) Classifying entries into sections.
update-llm-poolWorkflow for updating the LLM landscape paper pool (section/x_llm_papers.md) using fetch_llm_papers.py. Covers full re-fetch, resume from checkpoint, and adding new topics. USE FOR: Refreshing citation counts, expanding topic coverage. DO NOT USE FOR: Adding hand-curated entries to section files (use add-new-entry), updating RAG/Agent citation sections in best_practices.md (use update-cite-count).