# Ocena pomysłu na content z linku, artykułu lub premiery

> Twój agent czyta każdy udostępniony link także pod kątem contentu, ale odzywa się tylko wtedy, gdy pomysł przejdzie twardy filtr.

Canonical: https://dawidgac.com/pl/skills/ocena-pomyslu-na-content-ai
Opublikowano: 2026-09-22

## Co robi

Kiedy wklejasz agentowi artykuł, link, premierę narzędzia albo zrzut ekranu cudzej pracy, agent najpierw w pełni odpowiada na Twoje pytanie. Dopiero potem dopisuje krótką, oddzieloną notkę o potencjale contentowym albo nie dopisuje nic. Domyślnie odrzuca: temat nasycony na Twoim rynku, brak kąta, który tylko Ty możesz zająć, brak dowodów, samo streszczenie ogłoszenia. Pomysł, który przejdzie, dostaje nazwany hak, najtańszy format, okno czasowe i trafia na Twoją listę pomysłów. Zmiany na platformach, od których zależy Twoja praca, zawsze dostają notkę, zadanie i badanie tego samego dnia.

## Kiedy używać

- Publikujesz content i codziennie wklejasz agentowi linki, artykuły i premiery.
- Masz przewagę na konkretnym rynku lub w konkretnym języku i chcesz ją wykorzystać szybciej.
- Gubisz pomysły, które pojawiają się w rozmowach z agentem.

## Kiedy nie używać

- Nie publikujesz contentu.
- Chcesz, żeby agent generował pomysły na zamówienie. Ten skill tylko filtruje to, co udostępniasz.
- Pracujesz z agentem wyłącznie nad własnym kodem i danymi. Lens wtedy się nie włącza.

## Tabela decyzyjna

| Co udostępniasz | Co robi agent |
| --- | --- |
| Własny kod, logi, dashboard | Odpowiada. Bez notki contentowej. |
| Artykuł spoza Twoich tematów | Odpowiada. Zwykle bez notki. |
| Artykuł z Twojego głównego tematu | Odpowiada, potem notka: hak, format, okno czasowe albo jawne odrzucenie z powodem. |
| Zmiana cennika lub API platformy, od której zależysz | Odpowiada, zawsze notka, zadanie i badanie tego samego dnia. |
| Mówisz, żeby rozwinąć pomysł | Dopiero teraz startuje research i rozwijanie pomysłu. |

## Czego potrzebujesz

### An AI coding agent: Claude Code, Codex CLI or Cursor

wymagane, aplikacja: https://code.claude.com/docs/en/overview

Uruchamia filtr. Wystarczy agent, który czyta plik instrukcji w markdown.

1. Zainstaluj jednego agenta według jego oficjalnej dokumentacji: Claude Code (code.claude.com/docs), Codex CLI (developers.openai.com/codex) albo Cursor (cursor.com/docs).
2. Umieść folder szablonu tam, skąd Twój agent wczytuje skille lub instrukcje, zgodnie z krokami instalacji.
3. Sprawdź, czy agent umie przeczytać stronę: wklej link do publicznego artykułu i poproś o streszczenie w jednym zdaniu. Jeśli nie umie, wklejaj tekst artykułów.

### X API (official)

opcjonalne, API: https://docs.x.com/x-api/posts/lookup/introduction

Opcjonalne. Pozwala agentowi przeczytać post lub wątek z linku do X, bo strony X zwykle nie ładują się przez zwykłe pobranie strony. Bez tego wklejasz treść posta do rozmowy.

1. Załóż konto deweloperskie na developer.x.com i utwórz projekt oraz aplikację w konsoli.
2. Sprawdź w konsoli aktualne opcje dostępu i cennik, zanim zaczniesz na nim polegać.
3. Wygeneruj dla aplikacji token typu app-only. Zapisz go w zmiennej środowiskowej na swoim komputerze albo w menedżerze haseł. Nigdy nie wklejaj go do rozmowy i nie dodawaj do repozytorium.
4. Pozwól agentowi czytać token z tej zmiennej i wywoływać endpoint pobierania postów (posts lookup) tylko wtedy, gdy udostępniasz link do X.

## Instalacja

1. Skopiuj folder z plikami SKILL.md i CONTEXT.template.md.
2. Claude Code: umieść go jako .claude/skills/content-lens/ w projekcie albo w ~/.claude/skills/content-lens/ dla wszystkich projektów.
3. Codex lub Cursor: wklej treść SKILL.md do AGENTS.md w projekcie.
4. Inny agent: wklej SKILL.md do pliku instrukcji projektu lub promptu systemowego.
5. Zmień nazwę CONTEXT.template.md na CONTEXT.md i uzupełnij rynek, tematy, listę konkurentów, formaty z kosztem, listę pomysłów i platformy, od których zależysz.

## Działa, jeśli

- Po wklejeniu linku agent najpierw odpowiada na pytanie, a notka contentowa stoi osobno na końcu.
- Po wklejeniu logu z własnej aplikacji odpowiedź nie zawiera żadnej notki contentowej.
- Każda notka ma nazwany hak i konkretny format albo jawne odrzucenie z powodem z tabeli.
- Twoja lista pomysłów dostaje nowy wiersz z datą, hakiem, formatem i linkiem w tej samej turze.
- Samo wklejenie linku nie uruchamia wyszukiwania w sieci ani subagenta, poza wyjątkiem dla zmian na platformach.

## Wymagania

- Agent, który czyta plik instrukcji w markdown (Claude Code, Codex, Cursor lub inny).
- Uzupełniony CONTEXT.md.
- Miejsce na listę pomysłów, do którego agent może pisać.
- Opcjonalnie: dostęp do oficjalnego X API, jeśli chcesz, żeby agent czytał posty z linków do X.

## FAQ

### Czy agent będzie dopisywał pomysły do każdej odpowiedzi?

Nie. Domyślnie odrzuca i milczy. Notka pojawia się tylko wtedy, gdy pomysł ma nazwany hak i format, albo gdy temat dotyczy Twojego głównego tematu lub platformy, od której zależysz.

### Czy ocena linku zużywa czas na research?

Nie. Notka opiera się na tym, co agent już wie. Research startuje dopiero, gdy powiesz, że chcesz rozwinąć pomysł. Wyjątkiem są zmiany na platformach z Twojej listy zależności.

### Co jeśli nie mam społeczności ani regularnych spotkań z nią?

Zostaw pole listy tematów do dyskusji puste. Druga, cicha poprzeczka wtedy się wyłącza.

### Skąd agent wie, co jest nasycone na moim rynku?

Z listy konkurentów, którą wpisujesz w CONTEXT.md, z opisu Twojego rynku i z własnej wiedzy agenta. Jeśli lista jest pusta, agent prosi Cię o nią. To szybka ocena. Pełne sprawdzenie konkurencji robisz w kroku rozwijania pomysłu.

## Gdzie to pasuje

Działa jako filtr na wejściu. Pomysły, które przejdą, trafiają na listę, a rozwijasz je w osobnym kroku researchu. Dobrze łączy się z szablonem doprecyzowania przed działaniem, który pilnuje, żeby agent nie zgadywał, co masz na myśli, oraz z szablonem orkiestratora, jeśli research rozdzielasz na kilku agentów.

## Źródła

- Claude Code docs: skills: https://code.claude.com/docs/en/skills (dostęp 2026-09-22)
- Codex docs: AGENTS.md: https://developers.openai.com/codex/guides/agents-md (dostęp 2026-09-22)
- Cursor docs: rules: https://cursor.com/docs/context/rules (dostęp 2026-09-22)

## Pliki

### SKILL.md

Metoda: kiedy lens się włącza, tabela odrzuceń, tryb menedżera, wybór formatu, zapis pomysłów.

Pobierz: https://dawidgac.com/pl/skills/ocena-pomyslu-na-content-ai/files/SKILL.md

````markdown
---
name: content-lens
description: Reads anything the user shares from outside their own work (a link, article, release, screenshot, post, competitor page) for content potential, after answering their actual question in full. Use it whenever the user pastes or links an external artifact; it stays silent unless an idea clears a strict kill test.
---

# Content Lens

The user publishes content. People like that share articles, links, releases and screenshots all day,
and some of those artifacts are the raw material for their next post. This skill makes you read each
external artifact twice: once to answer what they asked, once for content potential.

Most artifacts have no content potential. Silence is the correct output far more often than a
suggestion. The lens only stays useful while it stays quiet.

Read `CONTEXT.md` next to this file before the first use in a session. It holds the user's market and
language edge, their content topics, their competitors, their surfaces and what each costs, where cleared
ideas get captured, and which platforms their work depends on.

If `CONTEXT.md` is missing, or a field you need is blank, ask the user for it in the language they write
in, one field at a time, and write the answer into `CONTEXT.md` so you never ask twice. For example:

- English: "Add your competitor list: the accounts, channels or sites that already cover your topics in your market."
- Polish: „Dodaj swoją listę konkurentów: konta, kanały lub strony, które już publikują na Twoje tematy na Twoim rynku."

The template ships with no competitors, topics or platforms. Never invent them. Until the competitor list
exists, judge saturation from what you already know and say in the read that it was not checked against
a list.

## Before you start / What you need

- **An AI coding agent** that reads a markdown instruction file: Claude Code, Codex CLI or Cursor.
- **A way to read what the user shares.** For public web pages, use the agent's built-in web fetch. If the
  agent has none, or a page does not load, ask the user to paste the text.
- **X posts (optional).** X pages usually do not load for a plain web fetch. If the user has set up the
  official X API (developer.x.com), read the post through its posts lookup endpoint with the access token
  the user keeps in their own environment. Otherwise ask the user to paste the post text. Never use an
  unofficial scraper or a third-party proxy, and never ask the user to paste a token into the chat.
- **A filled-in `CONTEXT.md`** and a place for the idea list you are allowed to write to.

## 1. When the lens fires

It fires on anything that originated outside the user's own world:

- a pasted article, announcement, changelog or paper
- a link to anything
- a tool, product, model or feature release
- a screenshot of someone else's work
- a post, thread, video or clip
- a competitor's page, offer or pricing
- a piece of news or a platform policy change

It does NOT fire on:

- the user's own code, repositories, configs, logs, error traces, metrics or dashboards
- screenshots of the user's own app or product
- questions about the user's own system
- anything shared purely as a work instruction ("fix this", "why is this failing")

**The two-part test. Both halves must hold:**

1. Did it originate outside the user's world?
2. Does it carry information their audience does not already have?

If either half fails, the lens stays off. Answer the question and stop.

## 2. Shape: a coda, never the lead

The question the user asked is the response. Answer it completely, on its own terms, as if this skill
did not exist.

The content read comes after. It is short, and it sits visually apart: its own line or its own small
block, clearly appended. Never weave it into the answer.

Why this rule exists: a lens that turns a technical question into a marketing pitch gets switched off,
and then it catches nothing.

## 3. Kill by default

Over-firing is the worse of the two failures. A missed artifact costs one piece of content. A coda on
everything trains the user to stop reading codas, and after that the lens is worthless.

Output nothing at all when any of these hold:

| It dies when | Because |
|---|---|
| The topic is already saturated in the user's market or language (see `CONTEXT.md`) | Their edge is being early or better there; the fifth voice brings nothing |
| No angle exists that the user can uniquely claim | If anyone could make it, nobody has a reason to watch it from them |
| It sits on no content topic they already run | A new topic costs a slot in a production budget that is already full |
| It needs receipts they do not have | A claim without proof damages the brand instead of building it |
| The only possible take is summarising the announcement | That is aggregation; the audience can read the source |
| It has neither a decay window nor evergreen value | Not urgent and not durable means it is nothing |

**Banned output: enthusiasm without an angle.** "This could make a great video" with no named hook and no
named surface is worse than silence. It costs attention and returns no decision. If you cannot name the
hook in one sentence, the read has failed; output nothing.

## 4. What the read scores on

Answer these three from what you already know. Do not research.

1. **Coverage in the user's market.** Is it uncovered, or badly covered, in their language or market?
   Check it against the competitor list in `CONTEXT.md`. Badly covered is often the better opportunity:
   there is a named thing to be right about.
2. **Decay window.** How long until everyone has covered it? Hours, days, weeks, or evergreen?
3. **What the user adds.** What do they bring that the source lacks: their own numbers, their customers'
   or clients' results, hands-on testing, a contrarian read they can defend?

If you cannot answer both 1 and 3, the idea dies.

## 5. Manager mode on core topics

On the topics listed as core in `CONTEXT.md`, drop the terse coda and give an active manager read. Deliver
exactly one of these two shapes:

**Cleared:**

```
Content read: [hook, one sentence]
Surface: [cheapest surface that captures it]
Timing: [decay window, e.g. "within 48 hours" or "evergreen"]
Why now: [one line, from what is already known]
```

**Killed:**

```
Content read: kill. [which row of the kill table, one clause]
```

Outside the core topics, kill-by-default governs: most artifacts get no line at all.

## 6. Name the surface, not "a video"

Pick the cheapest surface that captures the value. The user's surfaces and their production cost live in
`CONTEXT.md`. A neutral example list, cheapest first:

- community question or poll: one question the audience can argue with
- social post: a repurpose or one sharp observation
- short vertical video: one idea, one number
- newsletter item: a paragraph with a take
- blog post: evergreen and searchable
- long video: last resort, and say so explicitly

Recommend the long, expensive format only when nothing cheaper carries the idea. Say why when you do,
because production capacity is usually the binding constraint.

## 7. Capture, do not just mention

When an idea clears, write it to the user's idea list (location and format in `CONTEXT.md`) in the same
turn. One line per idea: date, hook, surface, decay window, source link.

Confirm the capture back in one line: `Captured: [hook] -> [surface]`. A cleared idea that lives only in
chat history is lost.

## 8. Second, silent bar: discussion topics (optional)

If `CONTEXT.md` names a community, call or discussion space, apply a second, lower bar to every external
artifact, including ones the content lens killed: would this make a good discussion segment (news value,
relevance to members, a teachable pattern)?

If yes, capture it silently to the discussion-topics list in `CONTEXT.md`. Do not mention it in the reply.
Kill-by-default governs the public coda only; this capture is cheap and invisible.

## 9. Exception: platform shifts always surface

A product, API, model, pricing or policy launch or change by a platform the user's work depends on
(listed in `CONTEXT.md`) is never killed as "just an announcement", "no topic" or "aggregation". For this
class:

1. It always gets a content read, even outside core topics.
2. It always gets a research step the same day: tell the user and start one, or run it if the user has
   told you to develop such shifts automatically (see `CONTEXT.md`).
3. It always becomes a task in the user's task list, with the decay window stated.

Why this exception exists: a platform change goes stale fastest, so a shift that is noticed but never
acted on is the most expensive miss the lens can make.

## 10. The lens never triggers research by itself

The inline read is a fast read from what you already know. It never starts a research task, a web search
or a subagent. Sharing a link must never cost the user a research run.

Research starts only when the user says to develop the idea, in whatever words they use ("develop
this", "draft it"). Those are sequential steps, never simultaneous. The platform-shift exception in
section 9 is the only case where a research step is scheduled without that phrase.

## Worked example

The user runs a home-cooking video channel with a weekly newsletter. They paste a link: their newsletter
tool announces that paid subscriptions become free to switch on for small senders next month. They ask:
"Does this change anything for my newsletter?"

1. Answer in full: what changes, whether their setup is affected, what to do before the date.
2. Two-part test: external, yes. New to their audience of other home cooks who run small newsletters, likely yes.
3. The newsletter tool is on the dependency list in `CONTEXT.md`, so section 9 applies.
4. Coda:

```
Content read: "Your newsletter tool now lets you charge readers; here is the setting to check first"
Surface: short vertical video
Timing: within a week, before others explain it
Why now: the change lands next month and the setting is easy to miss
```

5. Capture the idea, add a task, note the research step.

Counter-example: the same user pastes a big-tech keynote summary about a feature for enterprise teams and
asks what it means. Answer the question. No topic, no receipts, only a summary take: no coda at all.

## Failure modes to watch for

- The coda arrives before the answer, or blends into it.
- A coda says "great content idea" with no hook and no surface.
- A research task starts because a link was shared.
- A killed idea gets a paragraph explaining why it was killed, outside manager mode.
- The long format gets recommended by default.
- A platform shift passes with no task created.
````

### CONTEXT.template.md

Twój rynek, tematy, formaty z kosztem, lista pomysłów i platformy, od których zależysz.

Pobierz: https://dawidgac.com/pl/skills/ocena-pomyslu-na-content-ai/files/CONTEXT.template.md

```markdown
# Content Lens: your context

Copy this file to CONTEXT.md next to SKILL.md and fill in every blank (______). Example lines only show the shape of an answer; delete them once you have written your own. Never put passwords, access keys or card numbers here.

## Your market and language edge

(Where you publish and what makes you early or different there: a language, a country, a niche, a type of audience.)
Your answer: ______
Example (replace it, this is not your data): Spanish-language content on budget home cooking.

## Your audience

(Who watches or reads you, in one or two lines. The two-part test asks whether an artifact carries information they do not already have.)
Your answer: ______
Example (replace it, this is not your data): home cooks who batch-prepare meals for the week.

## Core content topics

(The topics you already publish on. The lens gives a full manager read on these and stays mostly silent elsewhere.)
Your answer: ______
Example (replace it, this is not your data): weekly meal prep, cheap kitchen tools, grocery budgeting.

## Your competitors

(Add your own list: the accounts, channels, newsletters or sites that already cover your topics in your market. The lens checks each topic against this list to judge whether it is saturated. The agent asks for this list if it is blank.)
Your answer: ______
Example (replace it, this is not your data): three channels in my language on budget cooking, one recipe newsletter, one food blog.

## Surfaces and their cost

(Every format you publish, cheapest first, with a rough production cost in time. The lens recommends the cheapest one that captures the idea.)
Your answer: ______
Example (replace it, this is not your data): community question: 5 minutes
Example (replace it, this is not your data): short vertical video: 1 hour
Example (replace it, this is not your data): long video: 2 days

## What you can bring that sources lack

(Your receipts: your own data, client or customer results, hands-on tests, a stance you can defend. An idea that needs receipts you do not have dies.)
Your answer: ______
Example (replace it, this is not your data): my own weekly grocery receipts, side-by-side tests of recipes I cook.

## Idea list

(Where cleared ideas get captured and in what format: a file path in your project, a notes app page, a task board column.)
Your answer: ______
Example (replace it, this is not your data): ideas.md in this project, one line per idea.

## Task list

(Where platform-shift tasks go.)
Your answer: ______
Example (replace it, this is not your data): the "This week" column of my task board.

## Discussion-topics list (optional)

(If you run a community, call or discussion space: where silent discussion-topic captures go. Leave blank to switch this bar off.)
Your answer: ______
Example (replace it, this is not your data): discussion-topics.md, reviewed before each community session.

## Platforms your work depends on

(Every platform whose launches, pricing or policy changes affect you or your audience. A change by one of these always surfaces and always gets a same-day research step and a task.)
Your answer: ______
Example (replace it, this is not your data): my video platform, my newsletter tool, the recipe site I publish on.

## Platform-shift research

(Should the agent start the same-day research step on its own, or ask you first?)
Your answer: ______
Example (replace it, this is not your data): ask first.
```