ReddRadar
Agent skill
classify-temp-entries-to-section
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.
Install this agent skill to your Project
npx add-skill https://github.com/kimtth/awesome-azure-openai-llm/tree/main/.agent/skills/classify-temp-entries-to-section
SKILL.md
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:
- Identify the target section — Based on the title of each entry determine which section file it belongs to mark down files under
section/and the specific section heading within that file. - Insert into sections — Once classified, entries should be moved from
temp_entries.mdto the appropriate section files (azure.md,applications.md,models_research.md,best_practices.md,tools_extra.md) under the correct section headings. - 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.
- Update temp_entries.md — After classification and insertion, add Check emoji ✅ to the entry in
temp_entries.mdto keep it clean and track which entries have been processed.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
kimtth/awesome-azure-openai-llm
add-new-entry
Workflow 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.
kimtth/awesome-azure-openai-llm
update-app-count
Workflow 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.
kimtth/awesome-azure-openai-llm
update-cite-count
Guidelines 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.
kimtth/awesome-azure-openai-llm
update-llm-pool
Workflow 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).
davila7/claude-code-templates
verl-rl-training
Provides guidance for training LLMs with reinforcement learning using verl (Volcano Engine RL). Use when implementing RLHF, GRPO, PPO, or other RL algorithms for LLM post-training at scale with flexible infrastructure backends.
davila7/claude-code-templates
openrlhf-training
High-performance RLHF framework with Ray+vLLM acceleration. Use for PPO, GRPO, RLOO, DPO training of large models (7B-70B+). Built on Ray, vLLM, ZeRO-3. 2× faster than DeepSpeedChat with distributed architecture and GPU resource sharing.
Didn't find tool you were looking for?