agentleFS
sergebulaevsergebulaev/instagram-skills/skills/ig-hashtag-strategist/SKILL.md

ig-hashtag-strategist

Skill692 starsChanged 5 months agoMITView on GitHub

Build a sized Instagram hashtag set for a post using the 2026 reality that 3 to 5 well-chosen tags beat 30 random ones. Sizes each tag as niche (under 50k posts), mid (50k to 500k), or broad (500k+), then assembles a 2-3 niche, 1-2 mid, 0-1 broad mix that a small or mid account can actually rank in, matched to the post content and rotated to avoid spam patterns. Use to choose hashtags for a caption, carousel, or Reel. Not for writing the caption itself (use ig-caption-writer).

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every tag must describe the actual content.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
SKILL.md

Instagram Hashtag Strategist

Pick 3-5 hashtags that actually help, sized so the post can rank. The 30-tag wall is dead: in 2026 hashtags work as topic labels, and a small account ranks in niche tags, not in million-post broad ones. This skill builds the sized set.

When to use

  • User has a caption, carousel, or Reel and needs hashtags
  • User is still posting 20-30 generic tags and wants the 2026 approach
  • User wants tags sized to where their account can actually rank

The model: size, not volume

A tag's size is its total post count. The strategy is a mix so the post ranks in the small tags while touching the bigger ones.

TierPost countRoleUse
Nicheunder 50kwhere a small/mid account can actually rank for hours2-3
Mid50k - 500kenough audience, beatable competition1-2
Broad500k+a brief category-label touch, ranks for minutes0-1

Default: 3-5 total. Full reasoning in ../../references/hashtag-strategy.md.

Steps

  1. Get the post. The caption, carousel topic, or Reel subject, plus the target audience and the account's rough size (so the niche/mid split fits).
  2. Extract topics. Pull the 3-5 real topics the post is about (the subject, the niche community, the format, the outcome).
  3. Generate candidates per tier. For each topic, propose niche, mid, and broad candidates. Niche tags are specific and long-tail (#notionforfreelancers); broad tags are single common words (#marketing).
  4. Size each candidate. Estimate the tier from specificity (the API does not expose counts, so use judgment and tell the user to verify counts in the app's search). Flag any obviously generic or flag-prone tags (#follow4follow, #like4like) to drop.
  5. Assemble the set. 2-3 niche + 1-2 mid + 0-1 broad, total 3-5. Drop the broad slot if nothing genuinely fits. Every tag must match the content.
  6. Check the match. Reject any tag that is popular but off-topic; a mismatch mistrains the recommendation engine and lowers reach.
  7. Rotate. Tell the user to vary the set per topic, not reuse one block on every post (identical sets across many posts read as automation).
  8. Output. The 3-5 set, each tagged with its tier and a one-line why, plus placement guidance (end of caption or first comment).

Output format

Sized set (4 tags):
  #notionforfreelancers   niche   the exact community this post serves
  #freelanceworkflow      niche   long-tail, low churn, rankable
  #productivitytips       mid     warm relevant audience, beatable
  #notion                 broad   category label, one touch

Placement: end of the caption or the first comment. Rotate the niche tags per topic.

Hard rules

Global voice rules: see root SKILL.md Voice rules. Additional skill-specific rules:

  • 3-5 tags total. Never output a 30-tag block.
  • Every tag must describe the actual content. No popular-but-off-topic tags.
  • At most one broad tag; drop it if nothing fits.
  • Flag and remove engagement-farm tags (#follow4follow, #like4like) and any known flagged tags.
  • Hashtags go at the end of the caption or in the first comment, never mid-sentence.
  • Rotate sets per topic; do not hand the user one block to paste forever.

Anti-patterns (skill will refuse)

  • Outputting 20-30 hashtags.
  • A "viral hashtag pack" of generic broad tags.
  • Tags that do not match the post to chase a bigger audience.
  • Hiding 30 tags behind dots to "look clean".
  • All-broad sets a small account cannot rank in.

Resources

  • ../../references/hashtag-strategy.md - the full 2026 sizing model and recipe
  • ../../references/algorithm-heuristics.md - why sends and saves, not hashtag feeds, drive reach

Related skills

  • ig-caption-writer - writes the caption the hashtags attach to
  • ig-carousel-planner - the carousel whose caption carries the set
  • ig-content-planner - rotate tag themes across a week

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.