Agent skill · Security

skill-index-updater

Add GitHub skill repos to the ASM index: clone, audit, eval, regenerate index, rebuild catalog, open PR. Use when given GitHub URLs to onboard. Don't use for authoring (skill-creator), improving (skill-auto-improver), or install (asm install).

luongnv89github.com/luongnv89GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add luongnv89/asm --skill skill-index-updater --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 14 KB
Bundled scripts: none
Version: 1.3.0
Declared author: luongnv89
Allowed tools: BashReadWriteEditGrepGlobWebFetchAgent
Requires: Claude Code
Path: skills/skill-index-updater/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 782
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Skill Index Updater You are adding new skill repository sources to the ASM (Agent Skill Manager) curated index. This is the pipeline that powers the skill catalog at https://luongnv.com/asm/ — every repo you add here becomes discoverable and installable by thousands of users. ## Example ``` User: add github.com/anthropics/skills to the index Skill output: Step 1: Parsed 1 URL → anthropics/skills (NEW) Step 2: Discovered 14 SKILL.md files Step 3: Audit OK on 14/14, eval scores 71–94 Step 6–8: data/skill-index-resources.json + data/skill-index/anthropics_skills.json updated, catalog rebuilt Step 10: PR #312 opened — feat(index): add anthropics/skills (14 skills) ``` ## Repo Sync Before Edits (mandatory) Before modifying any files, pull the latest remote branch: ```bash branch="$(git rev-parse --abbrev-ref HEAD)" git fetch origin git pull --rebase origin "$branch" ``` If the working tree is dirty: stash, sync, then pop. If `origin` is missing or conflicts occur: stop and ask the user before continuing. ## Input The user provides one or more GitHub repository URLs. These can be in various formats: - `https://github.com/owner/repo` - `github.com/owner/repo` - `github:owner/repo` - `ow

What's inside
Steps it walks through
  1. Example
  2. Repo Sync Before Edits (mandatory)
  3. Input
  4. Pipeline
  5. Step 1: Parse and Validate Input URLs
  6. Step 2: Discover Skills in Each Repository
  7. Step 3: Audit and Evaluate Discovered Skills
  8. Step 4: Check for Existing Repos to Update
  9. Step 5: Create Feature Branch
  10. Step 6: Update skill-index-resources.json
  11. Step 7: Generate Index Files
  12. Step 8: Rebuild Website Catalog
  13. Step 9: Verify Everything
  14. Step 10: Commit, Push, and Create PR
Ships with 1 file
  • docs/README.md
Commands it runs
git fetch origin
git pull --rebase origin "$branch"
Clone to temp
git clone --depth 1 "https://github.com/{owner}/{repo}.git" "$TEMP_DIR/{repo}"
Find SKILL.md files (max 5 levels deep, matching ASM's discoverSkills)
find "$TEMP_DIR/{repo}" -maxdepth 5 -name "SKILL.md" -type f
asm eval "$TEMP_DIR/{repo}/{relPath}" --json
git checkout -b feat/index-add-{repo-names}
cd "$(git rev-parse --show-toplevel)"
npm run preindex
More from asm
All skills →
About this skill
What does the skill-index-updater skill do?

Add GitHub skill repos to the ASM index: clone, audit, eval, regenerate index, rebuild catalog, open PR. Use when given GitHub URLs to onboard. Don't use for authoring (skill-creator), improving (skill-auto-improver), or install (asm install).

How do I install it?

Run `npx skills add luongnv89/asm --skill skill-index-updater --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From luongnv89/asm, a repository with 782 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going