SuperAPI AI Directory

update-ai-tools

Agents & models

View repository

Updated 10-15 20:04

About this skill

AI tool documentation update

After adding/changing AI tools such as Skills and Agents, recursively update all README.md files and reflect them in the CHANGELOG.

Activation conditions

  • /update-ai-tools When the command is entered
  • When requested to "refresh tool docs", "update README", or "sync documentation"

Execution flow

1. 변경 감지 → 2. 개별 도구 README → 3. 디렉토리 README → 4. 루트 README → 5. CHANGELOG

Step 1: Detect changes

# 최근 변경된 AI 도구 파일 확인 (git 기준)
git diff --name-only HEAD
git diff --cached --name-only
git status --short

# skills/ 및 agents/ 하위 변경 파일 필터링
git diff --name-only HEAD -- skills/ agents/

Detection targets:

  • Newly added tools (SKILL.md, AGENT.md new)
  • Modified tools (SKILL.md, AGENT.md changed)
  • Deleted tools (directory deleted)

If there are no changes, notify the user and exit.

Step 2: Update individual tool README.md

Update the README.md in each changed tool directory.

Targets: skills/{name}/README.md, agents/{name}/README.md

Content to write in each README.md:

  • Skill/Agent name, description (based on SKILL.md/AGENT.md frontmatter)
  • Key features (extracted from the body)
  • How to use (invocation command, trigger keywords)
  • Directory structure (actual file list)

New tools: Create new README.md Modified tools: Rewrite the existing README.md based on the latest SKILL.md/AGENT.md Deleted tools: The corresponding README.md is also deleted (automatic when the directory is deleted)

If there are 3 or more changed tools, parallel processing with an agent team is recommended.

Step 3: Update directory README.md

skills/README.md와 agents/README.mdUpdate .

skills/README.md:

  1. Scan all skills/*/SKILL.mdScan
  2. Extract name and description from frontmatter
  3. Group by category (maintain the existing category structure)
  4. Rewrite the summary table + detailed section for each category

agents/README.md:

  1. Scan all agents/*/AGENT.mdScan
  2. Rewrite the summary table + individual detailed sections

Category classification criteria: Category guide Reference. Categories that do not exist can be created after being proposed.

Step 4: Update root README.md

README.mdUpdate only the following sections of (keep the remaining sections):

Update target Content
Resource list > Skills Full skill table (Name, Description) + count
Resource list > Agents Full agent table (Name, Description) + count
Directory structure Reflect the actual directory tree

Sections to keep: Installation method, supported agents, installation path, contribution method

Step 5: Reflect in CHANGELOG

/changelog Invoke the skill to record the changes in CHANGELOG.md.

Information to pass to the changelog skill:

  • List of added/modified/deleted tools
  • Change type (feat: new tool added, docs: documentation update, etc.)
  • Assignee (based on git author)

Parallel processing guide

Adjust the execution strategy based on the number of changed tools:

Number of changed tools Strategy
1~2개 Sequential processing
3 or more Agent team configuration (parallel by batch)

Configuration for parallel processing:

  • Individual tool README update agent (by batch)
  • Directory + root README update agent (after individual completion)

Precautions

  • If the existing README.md contains user-customized content, confirm whether to preserve it
  • Deleted tools are automatically removed from the directory README and root README
  • When updating the CHANGELOG, confirm the version type (patch/minor/major) with the user
  • This skill is disable-model-invocation: true, so only the user can invoke it