Index of every page on this site: llms.txt
All skills
alptugharun avatar

/pinterest-growth-engine

@2b12408
Run it yourself

Builds evidence-aware Pinterest keyword maps, seasonal opportunity clusters, board architecture, pin concepts, visual-series plans, and website traffic paths. Use for Pinterest research, visual search, trend planning, pin systems, and Pinterest-to-site growth.

  • 1 file
  • 3.3 KB
  • MIT
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/alptugharun/ai-social-media-toolkit/pinterest-growth-engine

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈71 tokens for metadata: the name and description. ≈750 when used: this file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈286 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Pinterest Growth Engine

Treat Pinterest as a visual discovery and search system, not only a social feed.

Evidence

Use live search, Pinterest data, trend tools, or user-provided exports when available.

Never invent search volume or trend status.

If only autocomplete / related terms are available, label them correctly.

When live Pinterest Trends API evidence is required, route discovery through pinterest-opportunity-radar first.

Do not scrape the consumer Pinterest UI as the primary evidence source.

Workflow

  1. Define niche, audience, market, season, and destination.
  2. Collect seed keywords.
  3. Expand into:
    • supporting keywords
    • long-tail keywords
    • seasonal keywords
    • commercial / product intent
    • informational intent
    • aesthetic / visual language
  4. Cluster keywords by intent.
  5. Identify visual patterns.
  6. Build content clusters.
  7. Map Pins to destination pages.
  8. Define measurement.
  9. If account analytics are available, compare current winners against the planned cluster before expanding production.

Opportunity Map

For each opportunity capture:

Cluster Intent Seasonality Evidence Visual pattern Destination Priority

Pin System

For each cluster create:

  • Hero Pin
  • Educational Pin
  • Checklist Pin
  • Comparison Pin
  • Seasonal variation
  • Search-led variation
  • Visual discovery variation

Visual-Series Rule

Maintain enough continuity to build recognition.

Possible constants:

  • subject
  • composition
  • camera
  • typography system
  • layout logic
  • brand mark

Possible variables:

  • season
  • color direction
  • style
  • environment
  • historical period
  • product
  • theme

Traffic Path

Every Pin should have a reason to exist:

Search / discovery intent → Pin promise → Destination match

Avoid sending users to irrelevant pages simply to generate clicks.

Output

Return:

  • Keyword map
  • Content clusters
  • Board / section plan when useful
  • 10–30 prioritized Pin concepts
  • Visual direction
  • Destination mapping
  • Seasonal calendar
  • Measurement plan

Measurement

Track when available:

  • impressions
  • saves
  • outbound clicks
  • CTR
  • top Pins
  • top boards
  • search-led landing-page sessions
  • conversions

Automation Mode

For recurring Pinterest operations:

  1. Let pinterest-opportunity-radar collect current evidence.
  2. Select only supported opportunities.
  3. Build the seven-variant Pin cluster.
  4. Map each Pin to a relevant destination.
  5. Keep publishing human-reviewed until API access, board mapping and destination checks are explicitly configured.
  6. After publishing, use organic analytics to identify winners and expand only the strongest clusters.

API Evidence

Pinterest API v5 can support organic reporting and Pin creation for approved/authenticated apps. The Trends API can return current growing keywords with WoW, MoM and YoY growth when access is available.

Never expose or commit a Pinterest access token.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 2b12408. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 2 months ago
metadata
{
  "version": "0.1.0",
  "author": "Alptuğ Harun"
}

README badge

README badge for alptugharun/ai-social-media-toolkit/pinterest-growth-engine