agentleFS
EronredEronred/aso-skills/AGENTS.md

aso-skills

AGENTS.md2.2k starsChanged 9 months agoMITView on GitHub

This repo contains ASO & App Marketing skills following the Agent Skills open standard. Compatible directories: .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/ Description drives discovery — agent reads all descriptions to decide which skill to load. Include "When the user wants to...", trigger keywords, and "For X, see Y skill" boundaries. iOS limits: Title 30 chars, Subtitle 30 chars, Keyword field 100 chars (comma-separated, no spaces), Description 4000 chars (not indexed for search), Promotional text 170 chars. Google Play limits: Title 30…

1 other project uses a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No filler, no hedging

    line 34
  2. Very specific:

    Run claude plugin validate --strict .

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Agent Guidelines

This repo contains ASO & App Marketing skills following the Agent Skills open standard.

Structure

skills/<name>/SKILL.md     — Skill instructions (required, <500 lines)
skills/<name>/references/  — Detailed docs loaded on demand (optional)
tools/integrations/        — API integration guides (Appeeky, Firebase, etc.)
tools/REGISTRY.md          — Capability matrix: which skill uses which tool

Compatible directories: .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

SKILL.md Format

---
name: skill-name          # Must match directory, lowercase+hyphens, 1-64 chars
description: ...          # Trigger phrases + scope boundaries, 1-1024 chars
metadata:
  version: 1.0.0
---

Description drives discovery — agent reads all descriptions to decide which skill to load. Include "When the user wants to...", trigger keywords, and "For X, see Y skill" boundaries.

Writing Style

  • Direct, actionable, second person
  • Tables for comparisons, numbered lists for steps
  • Bold for key terms, code blocks for examples
  • No filler, no hedging

App Store Reference

iOS limits: Title 30 chars, Subtitle 30 chars, Keyword field 100 chars (comma-separated, no spaces), Description 4000 chars (not indexed for search), Promotional text 170 chars.

Google Play limits: Title 30 chars, Short description 80 chars, Full description 4000 chars (indexed for search).

Key rules: Title has highest keyword weight. Don't repeat keywords across fields. Use singular forms. Don't include "app" or category names in keyword field.

Claude Code Plugin

The repo is also a Claude Code plugin marketplace: .claude-plugin/plugin.json (plugin manifest) and .claude-plugin/marketplace.json (catalog). Skills in skills/ are auto-discovered.

  • Bump version in plugin.json on every release, or installed users won't receive the update
  • Run claude plugin validate --strict . before pushing

Commits

feat(skill-name): ... / fix(skill-name): ... / docs: ...

Branches: feature/skill-name, fix/skill-name-desc, docs/desc

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.