Source profileQuality 85/100

aAAaqwq/AGI-Super-Team/skills/agent-skill-repository-index/SKILL.md

agent-skill-repository-index

Find and compare Daniel's reviewed GitHub skill sources. Use for high-star skill discovery, link checks, or safe installation, update, and removal of one selected skill.

Source repository stars
82
Declared platforms
0
Static risk flags
3
Last source update
2026-08-04
Source checked
2026-08-04

Decision brief

What it does—and where it fits

Route agents to reviewed upstream repositories without globally activating every repository. Treat popularity as a discovery signal, never as proof of quality or safety.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/aAAaqwq/AGI-Super-Team --skill "skills/agent-skill-repository-index"
    Safe inspection promptEditorial

    Inspect the Agent Skill "agent-skill-repository-index" from https://github.com/aAAaqwq/AGI-Super-Team/blob/a1b3bf19948a6f3da84347c920a23fc2799d8824/skills/agent-skill-repository-index/SKILL.md at commit a1b3bf19948a6f3da84347c920a23fc2799d8824. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Fast Workflow

      1. Resolve intent: discovery, comparison, installation, update, removal, or link verification. 2. Search already installed skills first. Reuse an equivalent Codex-native skill instead of adding a duplicate. 3. Shortlist at most three sources by capability, runtime compatibility,…

      Resolve intent: discovery, comparison, installation, update, removal, or link verification.Search already installed skills first. Reuse an equivalent Codex-native skill instead of adding a duplicate.Shortlist at most three sources by capability, runtime compatibility, maintenance, license, and risk class. Use stars only as a tie-breaker.
    2. 02

      Load Only What You Need

      Read references/repositories.md to find and compare sources.

      Read references/repositories.md to find and compare sources.Read references/star-snapshot.md only when the user asks about popularity or ranking.Read references/installing.md before installing, updating, linking, migrating, or removing a skill.
    3. 03

      Efficient Search

      Search metadata before opening files:

      Search metadata before opening files:Then inspect only the chosen skill directory. Scan risky behavior without printing secret values:
    4. 04

      Decision Rules

      For “redesign this landing page,” invoke the selected design skill. For “which high-star design skill repository does Daniel recommend, and install the safest option,” invoke this skill first.

      Prefer the original upstream, a Codex-native plugin, or a single passive instruction skill.Prefer a symlink for a clean reviewed local source that should update with its repository; prefer a normalized copy when Codex-specific adaptation is required.Keep catalogs, full runtimes, hooks, MCP servers, auto-updaters, deployers, tunnels, browser profiles, and persistent-memory systems inactive during discovery.

    Permission review

    Static risk signals and limitations

    Reads files

    low · line 19

    The documentation asks the agent to read local files, directories, or repositories.

    Inspect one candidate directory completely: `SKILL.md`, adjacent resources, license, Git remote, commit, worktree state, scripts, hooks, dependencies, credentials, network actions, and persistent state.

    Reads files

    low · line 33

    The documentation asks the agent to read local files, directories, or repositories.

    Then inspect only the chosen skill directory. Scan risky behavior without printing secret values:

    Network access

    medium · line 36

    The documentation includes network, browsing, or remote request actions.

    rg -l --hidden '(curl.+\|\s*(sh|bash)|sudo\b|rm\s+-rf|cookies?|auth|token|secret|hook|auto.?update|deploy|tunnel|daemon|memory)' /absolute/path/to/candidate

    Writes files

    medium · line 42

    The documentation asks the agent to create, modify, or delete local files.

    Prefer a symlink for a clean reviewed local source that should update with its repository; prefer a normalized copy when Codex-specific adaptation is required.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score85/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars82SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    aAAaqwq/AGI-Super-Team
    Skill path
    skills/agent-skill-repository-index/SKILL.md
    Commit
    a1b3bf19948a6f3da84347c920a23fc2799d8824
    License
    MIT
    Collected
    2026-08-04
    Default branch
    main
    View the original SKILL.md

    Daniel's Recommended High-Star GitHub Skills

    Route agents to reviewed upstream repositories without globally activating every repository. Treat popularity as a discovery signal, never as proof of quality or safety.

    Load Only What You Need

    • Read references/repositories.md to find and compare sources.
    • Read references/star-snapshot.md only when the user asks about popularity or ranking.
    • Read references/installing.md before installing, updating, linking, migrating, or removing a skill.
    • Run python3 scripts/verify_repository_index.py --repo-root /absolute/path/to/repos to verify index-to-clone identity. Add --remote when current GitHub reachability matters.

    Fast Workflow

    1. Resolve intent: discovery, comparison, installation, update, removal, or link verification.
    2. Search already installed skills first. Reuse an equivalent Codex-native skill instead of adding a duplicate.
    3. Shortlist at most three sources by capability, runtime compatibility, maintenance, license, and risk class. Use stars only as a tie-breaker.
    4. If a repository is an awesome-* catalog or has no root SKILL.md, use it for discovery only. Trace the selected item to its original upstream.
    5. Inspect one candidate directory completely: SKILL.md, adjacent resources, license, Git remote, commit, worktree state, scripts, hooks, dependencies, credentials, network actions, and persistent state.
    6. Classify it as DAILY, LIBRARY, QUARANTINE, or DUPLICATE. Do not install QUARANTINE capabilities without explicit authorization for their runtime effects.
    7. Follow references/installing.md. Install only the reviewed skill subdirectory, not the entire aggregator.
    8. Validate metadata and resources, then test one positive trigger and one negative trigger.
    9. Return an installation receipt containing upstream URL, local source, subpath, commit, license, class, target, install method, adaptations, checks, update method, and rollback method.

    Efficient Search

    Search metadata before opening files:

    rg -n --glob 'SKILL.md' '^(name|description):.*KEYWORD' /absolute/path/to/repos
    

    Then inspect only the chosen skill directory. Scan risky behavior without printing secret values:

    rg -l --hidden '(curl.+\|\s*(sh|bash)|sudo\b|rm\s+-rf|cookies?|auth|token|secret|hook|auto.?update|deploy|tunnel|daemon|memory)' /absolute/path/to/candidate
    

    Decision Rules

    • Prefer the original upstream, a Codex-native plugin, or a single passive instruction skill.
    • Prefer a symlink for a clean reviewed local source that should update with its repository; prefer a normalized copy when Codex-specific adaptation is required.
    • Keep catalogs, full runtimes, hooks, MCP servers, auto-updaters, deployers, tunnels, browser profiles, and persistent-memory systems inactive during discovery.
    • Preserve dirty repositories and existing targets. Never overwrite or delete them to complete an installation.
    • Fetch live star counts only when the user asks for a current ranking. Label the bundled figures as Daniel's July 2026 snapshot.

    For “redesign this landing page,” invoke the selected design skill. For “which high-star design skill repository does Daniel recommend, and install the safest option,” invoke this skill first.

    Alternatives

    Compare before choosing

    Computed 10023,781

    alirezarezvani/claude-skills

    app-store-optimization

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

    Computed 10014,225

    wanshuiyin/Auto-claude-code-research-in-sleep

    citation-audit

    Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

    Computed 1004,922

    dotnet/skills

    migrate-vstest-to-mtp

    Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing

    Computed 1002,504

    aaron-he-zhu/aaron-marketing-skills

    social-selling-planner

    Use when the user asks to "set up my founder social-selling routine", "build a daily engagement block for target accounts", or "turn funding / hiring signals into selling plays"; produces the founder/seller daily operating block — a time-boxed engagement-block spec (substantive value-add comments on target-account posts, never a pitch), warm-touch-before-ask cadence rules, trigger-response plays consuming the social-pulse-monitor B2B trigger watchlist (funding / hiring / launch signals), and a q