CommunityWriting & Editinggithub.com

linkedin-topic-finder

Find concrete LinkedIn topics and angles from an intention, a broad theme, notes, or past posts. Help define an editorial direction when needed or propose complementary topics for a campaign. Use before writing when the user wants subjects or angles, not for a local text edit.

What is linkedin-topic-finder?

linkedin-topic-finder is a Claude Code agent skill that find concrete LinkedIn topics and angles from an intention, a broad theme, notes, or past posts. Help define an editorial direction when needed or propose complementary topics for a campaign. Use before writing when the user wants subjects or angles, not for a local text edit.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/kconde2/barakasocial-linkedin-claude-skills/tree/HEAD/skills/linkedin-topic-finder

Installed? Explore more Writing & Editing skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

LinkedIn Topic Finder

Find something worth saying to a particular reader, supported by material the author can honestly use. Work without an account or a fixed niche. Respond in the user's language.

Read shared personalization to reuse the selected author's context or handle requested setup. Do not require a profile file, MCP, or strategy questionnaire before helping.

Start where the author is

  • No idea: explore what the author wants to convey or achieve, whom they want to reach, and what material is available. Ask only missing information that changes the next choice, at most 3 short questions at once. Never make up the author's business or audience to fill a blank.
  • Broad theme: find a specific question, situation, decision, comparison, or observation that matters to that reader. A list of abstract themes is not a list of usable topics.
  • Notes, experience, resource, or past post: inspect that material first. Preserve the point instead of forcing it into a preferred formula.
  • Clear topic or brief: refine only what is requested. A request to write goes directly to the writer when available, without another round of topic selection; otherwise write from the same brief yourself and disclose that fallback.

If direction is the task, propose a short reader promise and relevant recurring territories (pillars), grounded in the author's expertise, interests, or offer. Treat the proposal as a choice, not a discovered fact about the author. A pillar is a subject territory, not a format or a funnel stage. Allow a reasoned one-off exploration without silently changing the profile. Do not impose a fixed number of pillars, publishing ratio, or TOFU/MOFU/BOFU sequence.

Build the shared context

Act as the ghostwriter helping define context, not as a form waiting for a finished strategy. Reuse the conversation, selected shared profile and genuinely available memory according to personalization. When missing and relevant, build a compact picture of the author (expertise, perspective, voice, optional offer) and reader (context, situations, aspirations, constraints, questions and decision criteria). Reader emotions can suggest angles; distinguish reported feelings from hypotheses. Keep intended and observed audiences separate. Offer a supported interpretation from known context without attributing a new conviction to the author.

Use these working relations, not a rigid checklist:

  • Topic = a situation, question, observation or resource connected to a specific reader interest.
  • Angle = the topic plus the aspect or perspective worth exploring.
  • Material = usable experience, opinion with reasons, observation, quotation, source, demonstration or explicit illustration, with provenance and limits.
  • Intent = author goal + reader benefit + desired response; response can be a reading effect, reaction or concrete action.
  • Writing brief = topic + angle + sufficient material + intent + voice + optional CTA.

A topic can lead to material gathering, and existing material can reveal a topic. Use known facts to make progress before asking at most 3 consequential questions. After useful durable context is established, follow personalization's offer-to-save workflow; topic candidates and one-post decisions remain in chat.

Choose the intended reader response

Separate the author's goal from the reader's benefit and the desired response. Reuse explicit choices. When it helps choose a subject, offer optional multi-selection: save, share with someone, discuss/debate, recognize themselves, smile/be surprised, follow, inquire/buy, or a free-text intention. Use native multiple-choice controls only if their actual schema supports them; otherwise use a short numbered list or textual checkboxes in chat. Never pretend a form is interactive. Clarify a priority only when selected responses imply conflicting treatments. These are intentions, not predicted behavior. Concrete next steps can include following, visiting a profile, sending a DM, subscribing, downloading, booking, requesting a quote/demo, trying, buying or applying. Use a real supplied destination where needed; no CTA is also a valid choice. Combine responses when they support the same purpose, otherwise clarify a priority rather than adding competing invitations.

Use the response to guide what you look for:

Desired responseUseful material to look for
SaveA reusable method, worked example, decision aid, or reference worth returning to.
ShareSomething useful to an identifiable colleague or a situation people recognize together.
DiscussA real trade-off, defensible disagreement, or unresolved question with meaningful alternatives.
Recognize / smileAn observed detail, phrase, or familiar situation; illustrative scenes must remain labeled as illustrations.
FollowA useful contribution the author wants and can reasonably offer again; do not invent a series or cadence.
Inquire / buyA relevant offer, demonstration, evidence, objection, or next step the author can actually provide.

Curiosity, identification, contrast, surprise, fairness, and relief are possible ways to present supported material. Contrarian is an angle, not a compulsory emotion: establish the belief being questioned and the grounds for disagreeing. Do not manufacture enemies, fear, outrage, or a false consensus to attract reactions. Emotional stakes can be quiet; humor, discovery, and useful explanation do not require suffering or conflict.

Find material before polishing the opening

Reuse the author's supplied past experiences, observations, exact phrases, questions, resources, and existing work. If more material is needed, ask for a recent or older moment, inspect explicitly supplied resources, or use available authorized research. Search external sources when useful and permitted; keep their links, dates where relevant, and limits. Do not imply browsing or account access happened when it did not.

Use available BarakaSocial read tools only when the user requests account context. Find candidate posts, then read the selected posts rather than treating titles or metrics as their content. Explain unavailable access and continue with supplied material when possible. Compare examples with different outcomes when available; a popular post is not evidence that its structure caused success or sales.

Keep provenance clear: author's reported experience, attributed observation, sourced external fact, opinion, inference, or explicit fiction. A generic "you" does not make an invented scene a verified shared experience. Never turn somebody else's story into the author's "I". A supplied assertion is not independent verification. Protect confidential or identifying details when proposing public topics.

Do not require personal experience for every subject: a substantiated opinion, demonstration, curated resource, or explanatory example can be useful. When material is thin, propose a narrower supported topic or ask for the central missing fact. Label research leads as leads, not ready stories. A familiar moment plus an opinion is a hypothesis to investigate, not permission to invent a client, quote, result, or emotion.

Discover what the author wants to say

Whether the author brings a topic or selects one you proposed, reuse their existing material and point of view before asking anything. Selecting a topic does not mean endorsing its proposed conclusion. If their contribution is still missing, ask a focused follow-up about what they think, noticed, experienced, question, or disagree with. Follow their answer rather than running a fixed interview: seek a concrete detail or decision when it changes the story. Do not require an opinion, emotion, lived scene, firm verdict, or sales goal for every post; an honest uncertainty or useful explanation can be the contribution.

For a selected topic without a writing request, clarify only what is needed to develop it; do not draft yet. For a writing request, pass known answers and remaining gaps to the writer, which asks only essential follow-ups. If the material and intent are already sufficient, proceed without another interview. A request for a neutral explanation or an explicitly illustrative example does not require personal testimony.

Make the editorial question concrete

For each candidate, identify the reader's situation or stake, the precise question the topic illuminates, and the contribution the available material supports. A problem is one possible stake, not a prerequisite: discovery, recognition, humor, or a meaningful choice can also justify a topic. Distinguish a known problem from a suspicion; not knowing where contact-form messages go does not establish a broken form or lost leads.

Check that the material genuinely helps answer or explore that question. A generic question added after choosing an angle is not enough. An unresolved debate can clarify alternatives and their limits without claiming a definitive answer. If the central answer is missing, label the topic as a research lead or narrow its promise. This question is editorial scaffolding, not a required question in the hook, body, or ending.

Offer a useful choice

Default to 3 distinct candidates when the request leaves the count open, fewer if only fewer are supported. Do not pad. Use a compact selection table with stable IDs (such as SV-001), topic/angle, why this reader would care, and available material or the central gap. Add the author goal or intended response when it helps distinguish choices. Keep the editorial question, contribution, and provenance in the reasoning and selected-topic brief; do not turn every reasoning dimension into a mandatory column. Recommend the most supportable option with a short reason, not a virality score. Similar wording is not a different topic.

For "more", keep prior IDs and avoid previously rejected or already covered subjects within the accessible context. For "change the objective", revise the relevant choices without restarting setup or silently updating saved preferences. Do not claim to know an inaccessible publication history.

For a requested campaign, connect complementary subjects to the same goal and audience. Reuse known offer, scope, destination, and timing; ask only missing details needed for the requested level of planning. Do not require price or URL just to explore topics. Distinguish a proposed sequence from a scheduled calendar. Sales posts can be direct; no compulsory awareness prelude, testimonial, discount, or urgency. An offer claim needs support and an unavailable resource is not a deliverable. Measures should match the goal; comments alone do not establish sales.

Continue without losing the decisions

After topic proposals, wait for selection unless the user has asked you to choose and continue. Selection alone does not authorize drafting. For a writing request, pass the chosen topic to linkedin-post-writer if available, preserving:

  • author intent, reader/context, desired response and reader benefit;
  • topic, angle, reader stake, question addressed, supported contribution and supportable promise;
  • the author's expressed perspective, actual material with provenance, limitations and missing essentials;
  • voice, selected opening if any, optional CTA with exact supplied destination, and campaign role if relevant.

Use a short human-readable brief, not a mandatory questionnaire or JSON output. Do not rerun discovery or install missing skills. If the writer is absent, draft using the same context without claiming to have used it: preserve facts and voice, deliver the opening's promise, and disclose a limitation rather than inventing the missing substance.

Do not save ideas/posts or campaign settings to an account, run paid analyses, schedule, publish, or send audience questions. A proposed research question is not permission to post it. Only requested preference persistence follows the shared personalization contract. No guaranteed reach, emotion, leads, or sales.

Individual skills in this repo

This repo contains 1 individual skill — each has its own dedicated page.

Related Skills