agentleFS
postoncehqpostoncehq/instagram-mcp/skills/instagram-hashtag-generator/SKILL.md

instagram-hashtag-generator

Skill2 starsChanged 47 days agoMITView on GitHub

Pick a small set of specific, relevant Instagram hashtags for one post, carousel or Reel, sized from broad to niche. Use when the user asks for Instagram hashtags, a hashtag generator, which hashtags to use, or to clean up a long hashtag block before posting with the PostOnce Instagram MCP.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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 this post.

    line 29
  2. Distinctive:

    Prefer the words people search in plain English.

    line 32
  3. Distinctive:

    Check spelling and that the tag is in normal use.

    line 33
  4. Distinctive:

    Put tags at the end of the caption, on their own line.

    line 34
  5. Distinctive:

    If the user has a long list, keep the 3 to 5 that best match the post and explain in one line why the rest were cut.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 generator

Hashtags on Instagram help it understand what a post is about and who it's for. They're a label, not a reach hack. A few precise tags beat a block of 30 generic ones, and Instagram's own creator guidance recommends a handful of relevant tags.

Before choosing

Get or infer: what the post shows, the topic, the audience (who should find it), the account's niche, and the location if it matters (local business, event, travel). Read the caption if there is one.

How to pick

Choose 3 to 5 tags, one or two from each layer:

LayerWhat it isExample for a sourdough Reel
TopicWhat the post is about#sourdough
NicheThe specific angle or audience#sourdoughforbeginners
ContextPlace, format, event or community#londonbakers
Brand (optional)The account's own tag, if it uses one consistently#mayabakes

Rules:

  • Every tag must describe this post. A tag the post doesn't match sends it to the wrong people.
  • Skip broad, meaningless tags: #love, #instagood, #photooftheday, #viral, #explore, #fyp.
  • Skip banned or spammy-looking tags and long strings of near-duplicates (#food #foodie #foodporn #foodlover).
  • Prefer the words people search in plain English. Instagram search also reads the caption and keywords, so a clear caption does more than extra tags.
  • Check spelling and that the tag is in normal use; don't invent tags unless it's the user's brand tag.
  • Put tags at the end of the caption, on their own line. Don't put them in the first line.

Cleaning up an existing block

If the user has a long list, keep the 3 to 5 that best match the post and explain in one line why the rest were cut. PostOnce drops any hashtags past 30 automatically, so a longer list won't all publish.

Output

Return the recommended set on one line, ready to paste, then one short line per tag on why it fits. Offer one alternate set for a different audience if useful. If the user has the caption and media ready, offer to add the tags and publish or schedule with the postonce skill; confirm the Instagram account and the time before calling create_post.

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.