Add New Entry
Formats raw URLs into legend-styled wiki entries for the azure-openai-llm-wiki repo
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 21, 2026
- Environment
- Claude Code 2.x (agent harness)
⚠ This skill is no longer available upstream. Our re-check on Aug 10, 2026 couldn't find it any more (SKILL.md not found in repo tree). The test below is what we measured on Jul 21, 2026 and we're leaving it up as a record — but there is nothing left to install, so we've removed the command.
Found SKILL.md at .agent/skills/add-new-entry/SKILL.md; frontmatter has name+description. Spot-checked the 3 referenced scripts: 404 at the skill-relative path but 200 at repo-root code/ (fetch_github_description.py, get_github_dates.py, add_github_stars.py) — the skill is coupled to the repo root, not self-contained. No security smells. For OUTPUT I fed a 2-line temp.md (a GitHub repo + an arXiv paper) and produced a baseline_entries.md (my natural formatting) vs skill_entries.md (following the legend rules). Concrete measured differences: skill used dash+parens date `(Feb 2023)` and no emoji for the azure.md entry vs colon+brackets `[Jan 2025]` with the 📑 symbol appended inside `[DeepSeek-R1📑]` for the research entry; it put a real github-stars badge only on the GitHub line while baseline wrongly slapped ⭐ on the arXiv line too; descriptions dropped to 9 and 6 words vs baseline's verbose, name-repeating text. Baseline had no dates and identical formatting for both. The arXiv date I derived from the ID rule (2501→Jan 2025); the GitHub creation date would need the script to confirm.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 4/5
- Triggers reliably 5/5
- Output vs. baseline 7/10
- Docs & honesty 4/5
What Add New Entry does
A repo-maintenance skill that turns a raw temp.md checklist of URLs into properly formatted markdown entries for the azure-openai-llm-wiki section files, applying per-file legend rules (date format, star badges, emoji symbols, section names, 15-word descriptions). Triggers when adding new resources to that knowledge base; explicitly not for editing existing entries or restructuring sections. Relies on Python helper scripts under the repo's code/ directory to fetch GitHub descriptions, creation dates, and star counts.
How to install Add New Entry
Nothing to install: the source repository no longer has this skill. If the author brings it back, our daily re-check will pick it up and the command will reappear here.
Commands — how to trigger Add New Entry
-
/add-new-entryFormats raw URLs into legend-styled wiki entries for the azure-openai-llm-wiki repo
It also activates on plain-language prompts like these:
-
Add this new resource from temp.md to a section -
File this entry into the correct wiki page -
Add a new tool entry to the knowledge base
Frequently asked questions
- Is the Add New Entry skill free?
- Yes. The skill itself is free from kimtth/azure-openai-llm-wiki. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Add New Entry work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 21, 2026. Verdict: Works with setup. Found SKILL.md at .agent/skills/add-new-entry/SKILL.md; frontmatter has name+description. Spot-checked the 3 referenced scripts: 404 at the skill-relative path but 200 at repo-root code/ (fetch_github_description.py, get_github_dates.py, add_github_stars.py) — the skill is coupled to the repo root, not self-contained. No security smells. For OUTPUT I fed a 2-line temp.md (a GitHub repo + an arXiv paper) and produced a baseline_entries.md (my natural formatting) vs skill_entries.md (following the legend rules). Concrete measured differences: skill used dash+parens date `(Feb 2023)` and no emoji for the azure.md entry vs colon+brackets `[Jan 2025]` with the 📑 symbol appended inside `[DeepSeek-R1📑]` for the research entry; it put a real github-stars badge only on the GitHub line while baseline wrongly slapped ⭐ on the arXiv line too; descriptions dropped to 9 and 6 words vs baseline's verbose, name-repeating text. Baseline had no dates and identical formatting for both. The arXiv date I derived from the ID rule (2501→Jan 2025); the GitHub creation date would need the script to confirm.
- What is the Add New Entry SkillProof Score?
- 8.0/10 — installs cleanly 4/5, triggers reliably 5/5, output vs. baseline 7/10, docs & honesty 4/5.
- How do I install Add New Entry?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Add New Entry with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.