Skip to content
Skills Library
Marketing & content · Research

developer-audience-context

/developer-audience-context

Use when grounding developer marketing in a confirmed audience profile of persona, pains, alternatives, and trust signals. Not for inventing quotes, benchmarks, or audience facts.

Licence
Apache-2.0
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when grounding developer marketing in a confirmed audience profile of persona, pains, alternatives, and trust signals. Not for inventing quotes, benchmarks, or audience facts.

Original author description

Use when grounding developer marketing in a confirmed audience profile of persona, pains, alternatives, and trust signals. Not for inventing quotes, benchmarks, or audience facts.

How it works

  1. When this applies, and what it never does
  2. What you need before starting
  3. Building the ten-dimension profile
  4. Thin evidence and tempting fictions
  5. What you hand back
Original SKILL.md headings · 38 lines, 472 words
SKILL.md preview
---
name: developer-audience-context
description: 'Use when grounding developer marketing in a confirmed audience profile of persona, pains, alternatives, and trust signals. Not for inventing quotes, benchmarks, or audience facts.'
---

# Developer audience context

Ground developer marketing in what you can observe about the audience: who they are, where they gather, what hurts, what else they use, and the words they use. The result is an evidence profile delivered in chat. It stores nothing and invents nothing.

## When this applies, and what it never does

This applies when the user asks to define, update, or apply a developer audience profile for marketing work. The work is read-only: chat output only, with optional reads of public sources. No file writes, no canonical store, no credentials, no outreach, no publication.

There is no canonical audience store, and this skill never creates one. Every other marketing skill accepts supplied sources directly and must never require anything produced here.

Voice discipline matters: this skill records only observed audience evidence (how the audience speaks). How the brand should speak is prescribed by the `copywriting` voice work, not here. `TONE.md` or `VOICE.md` may be read as completed input, but never written.

## What you need before starting

- `product` (required): what is offered, in the user's own words or supplied docs.
- `evidence` (required): supplied docs, READMEs, issues, docs pages, or an explicitly requested read-only research pass. Mentions of tooling such as search consoles, rank trackers, or listeners are optional evidence inputs, never required dependencies.

## Building the ten-dimension profile

Work through these in order; each dimension is finished only when filled from evidence or explicitly marked unknown:

1. Collect all ten: product, persona, places, problems, alternatives, differentiators, verbatim language, trust signals, conversion actions, voice observations.
2. Give every item provenance: source and observation date. Verbatim language must be exact quotes with sources; never put a paraphrase inside quotation marks.
3. Check each trust signal against something real: docs quality, examples that run, error coverage, maintenance signs, license clarity. Each one cites the artifact observed.
4. State conversion actions as observed or plausible paths, each naming its evidence or flagged as an assumption. Never present them as guaranteed funnels.
5. Keep voice observations descriptive of the audience. No brand-voice prescription may appear.

## Thin evidence and tempting fictions

- Evidence too thin for a dimension: deliver the profile with the unknown explicit, and name the smallest evidence that would fill each gap.
- Fictional example material supplied as a format reference: borrow its shape only. Never copy its testimonials, numbers, or names as facts.
- Numeric claims you cannot verify (audience sizes, conversion benchmarks): mark them `UNVERIFIED` or omit them. Never let them stand as defaults.

## What you hand back

An audience profile in chat covering all ten dimensions, with per-item provenance, explicit unknowns, and exact verbatim quotes with sources. It is one optional input among supplied sources for other work; no other skill requires it. No file is created and the working tree stays untouched.
Files in this package (2)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · gosuda/dalcom-skills100Apache-2.0
FrancoStino/opencode-skills-collection100MIT
sickn33/agentic-awesome-skills100MIT

Database snapshot: 13.11.2026 · package version 0a16e745be96 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100audience-research
    Use to develop a deep, usable understanding of who a brand creates content for — sharp enough that every content skill resonates with them specifically. Run when the user says "who's my audience," "audience research," "target audience," "build a persona," "customer profile,"…
  • 90target-audience
    Define a brand's target audience with deep personas, psychographics, and ICP (Ideal Customer Profile). Use when the user says "target audience", "ideal customer", "customer persona", "audience persona", "ICP", "who is our customer", "define our audience", "audience research",…
  • 100product-marketing
    When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or…
  • 100product-marketing-context
    When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or…
  • 100product-marketing-context
    When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or…
  • 90target-audience
    Define a brand's target audience with deep personas, psychographics, and ICP (Ideal Customer Profile). Use when the user says "target audience", "ideal customer", "customer persona", "audience persona", "ICP", "who is our customer", "define our audience", "audience research",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.