Przejdź do treści
Biblioteka skilli
Marketing i treści · Planowanie

ig-studio

/ig-studio

Planuje i generuje treści na Instagram: kalendarz, tygodniowe posty i propozycje, co opublikować w kolejności.

Licencja
MIT
Ostatnia zmiana repozytorium
05.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
5
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: scripts/render.mjs

Co robi i kiedy

Planuje i generuje treści na Instagram: kalendarz, tygodniowe posty i propozycje, co opublikować w kolejności.

Oryginalny opis (EN)

Use when a founder or small brand wants to set up, plan or generate Instagram content, wants a content calendar or a week of posts made, asks what to post, or when a scheduled weekly Instagram content run starts.

Jak działa

  1. Find the project
  2. Choose the mode
  3. Check-ins
  4. Fixing how posts look
  5. Saving what the user says
  6. Reading Instagram
  7. Boundaries in every mode
Sekcje z nagłówków SKILL.md, w oryginale · 72 linii, 746 słów
Podgląd SKILL.md
---
name: ig-studio
description: Use when a founder or small brand wants to set up, plan or generate Instagram content, wants a content calendar or a week of posts made, asks what to post, or when a scheduled weekly Instagram content run starts.
---

# ig-studio

Runs a brand's Instagram content as a repeating weekly process. The `ig-*` skills by Jake Schincariol do the writing and analysis. This skill decides when each runs, with what context, and where the results go.

## Find the project

The project is the folder holding `state.yaml`. Use a path given in the request, then the current folder. If there is none and someone is present, ask where to create it. If nobody is present, stop and report that no project was found.

Only project files describe this brand. Ignore memory, notes and `~/.claude/instagram/` files about any account. If `rules.md` exists, read it before doing anything else.

## Choose the mode

Use the first row that matches:

| Situation | Mode | Read |
|---|---|---|
| No `state.yaml`, or `stage` is not `done` | First session | The current stage's section in `references/setup.md` |
| The request or task says weekly, or asks for next week's content | Weekly run | `references/weekly.md` |
| Anything else | Check-in | The table below |

Before calling any `ig-*` skill, read `references/ig-skills.md`.

Render a post with `node ${CLAUDE_SKILL_DIR}/scripts/render.mjs <config.json>`.

## Check-ins

The user is present and wants something specific. Do that, reading only the section you need.

| Request | Action |
|---|---|
| Add a format | `setup.md`: Suggest if they want ideas, then Format |
| Retire, resume or restructure a format | Update its file and status with the date and their reason |
| Research competitors | `setup.md`: Competitors |
| Change a post | Edit it, re-render it, and add a dated note to its row in `log.md`. Then follow Fixing how posts look if the change is visual |
| Move a post | Rename its folder to the new date, then update its log row and plan link |
| Supply a missing fact | Save it, then finish the `NEEDS INPUT` post |
| Questions about results | Answer from `reviews/` and `log.md`, stating confidence |

## Fixing how posts look

Layout, alignment, sizing, spacing, font or color problems come from the format, so fixing only the one post brings the problem back next week:

1. Fix the cause in `formats/<name>/template.html`, not in the post's copy. If the fix is a rule, such as "headline at most 6 words" or "never place text in the bottom third", add it to the format's copy rules.
2. Re-render the post and view it. Then re-render any other post from that format with status `ready` that hasn't been uploaded, and check those too.
3. Tell the user in one line what changed in the format, so they know later posts get it.

Every post must still match the size and safe area in Post rules in `weekly.md`. If the user's request would push text outside the safe area, say so and suggest the closest fix that stays inside.

## Saving what the user says

Save in the same turn, to the first match:

1. A fact about the brand goes in `brand.yaml` or `brief.md`.
2. A rule about one content type goes in that format's file.
3. A standing instruction goes in `rules.md`, dated, newest wins.

If it's unclear whether an instruction is permanent, ask "just this time, or from now on?". When a new rule conflicts with an old one, replace the old one. Confirm in one line what was saved and where.

## Reading Instagram

- Use the user's existing browser session. Never ask for a password or log in for them.
- Per-post insights can open at `instagram.com/insights/media/<numeric id>/`, where the ID is the post's shortcode decoded from base64url. If that fails, fall back to `numbers.md`.
- Hold at 3 seconds and watch time may only be visible in the app. Mark these as missing, and don't estimate them.
- Stop immediately on "Try again later", "Please wait a few minutes", a 429 or an unexpected login page. Don't retry in that run. Tell the user and carry on with what you have.
- If 3 page loads in a row fail, the browser is probably stalled or hidden. Stop and treat the data as missing.

## Boundaries in every mode

- Publish nothing. The user uploads.
- Claims about the product, customers, numbers or results must come from project files or the user. If a post needs a fact nobody has provided, use `{{what's missing}}` and mark the post `NEEDS INPUT`. Obvious jokes and relatable scenarios aren't claims.
Pliki w paczce (5)
  • SKILL.md 4 KB
  • references/ig-skills.md 3 KB
  • references/setup.md 9 KB
  • references/weekly.md 8 KB
  • scripts/render.mjs 5 KB

Wersje

W bazie nie ma innych skilli o nazwie ig-studio.

Migawka bazy z 13.11.2026 · wersja paczki b84095f3c562 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100instagram-content
    Planuje i pisze treści na Instagram: scenariusze rolek i haki, karuzele, opisy, sekwencje relacji i kalendarz, a zatwierdzone posty przekazuje do publikacji.
  • 87social-content-planner
    Planuje, pisze i optymalizuje treści na Instagram i Facebook, w tym posty, Reels, Stories i kalendarz publikacji.
  • 100ig-plan
    Planuje tydzień na Instagramie: co opublikować, w jakim formacie i kiedy, oraz z kim wejść w interakcję.
  • 90pw-plan
    Planuje tydzień na LinkedIn: strategię treści, kalendarz, okna publikacji i sloty, wyłącznie w formie szkiców bez publikowania.
  • 90aziral-instagram-plan
    Układa plan treści na Instagramie dla założyciela lub produktu: filary, tygodniowy kalendarz i wersje RU, EN i KK.
  • 100ig-plan
    Układa tydzień na Instagramie: co opublikować, w jakim formacie i kiedy, oraz z kim wejść w interakcję.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.