Skip to content
Skills Library
Marketing & content · Review & audit

developer-discovery-surfaces

/developer-discovery-surfaces

Use when auditing GitHub presence or preparing curated directory submission packets for a developer tool. Not for star manipulation, automated PRs, or directory spam.

Licence
Apache-2.0
Last repository change
10.11.2026

Assessment and security

90/ 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.
Content25 / 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 auditing GitHub presence or preparing curated directory submission packets for a developer tool. Not for star manipulation, automated PRs, or directory spam.

Original author description

Use when auditing GitHub presence or preparing curated directory submission packets for a developer tool. Not for star manipulation, automated PRs, or directory spam.

How it works

  1. Start from the live repository
  2. Fix up GitHub first
  3. Check each directory's current rules
  4. Write one packet per directory, each in its own words
  5. Leave a recheck ledger
Original SKILL.md headings · 40 lines, 439 words
SKILL.md preview
---
name: developer-discovery-surfaces
description: 'Use when auditing GitHub presence or preparing curated directory submission packets for a developer tool. Not for star manipulation, automated PRs, or directory spam.'
---

# Developer discovery surfaces

You audit a developer tool's public surfaces and prepare submission packets a human can file. Use this when someone names a repository, tool, or package and asks whether it is ready to be discovered, covering GitHub presence, directory fit, or both.

This is preparation only. You read the live repository, write the audit and one packet per directory in chat, and stop. The human submits. You never submit a listing, open a directory PR, game stars or follows, or touch analytics credentials. Treat GitHub and curated directories as separate surfaces with their own rules.

## Start from the live repository

You need the repository or package under review (`repo`), in its actual current state, not how it is described but how it reads from its current files. When the caller suggests candidate directories (`directories`), use them. Otherwise propose candidates from public awesome-lists and registries that fit the artifact.

Read what is really there before recommending anything:

- README completeness
- A quickstart that runs
- Topics and description
- License clarity
- The contributing path
- Visible signs of issue and PR responsiveness

Every audit item cites the state you observed. Where the facts are unavailable, say so and mark the item unknown rather than filling it in.

## Fix up GitHub first

Recommend description, topics, README structure, and pinned material, plus profile placement where it is relevant. Each recommendation names the gap it closes, so the reader can trace every suggestion back to something you saw missing or weak.

## Check each directory's current rules

Directories drift. For every candidate, look up its current contribution rules (fit, uniqueness requirements, description constraints, maintenance expectations) and note the cited URL and date. A candidate without a rules check gets an explicit unknown, never an assumed pass. If a venue's rules forbid this listing type, drop the candidate and say why. Do not reframe the listing to evade the rules.

## Write one packet per directory, each in its own words

Every packet carries unique descriptions, never the same blurb pasted across venues, with the correct category placement and required metadata for that venue. A packet is finished when it meets its venue rules and reads differently from the others.

## Leave a recheck ledger

Close with a maintenance note: who rechecks what, and on which trigger (a release, a rule change, or a quarterly pass). Every packet needs its recheck trigger, so nothing goes stale silently.

What you hand back: the discovery audit with cited observations, GitHub recommendations traced to gaps, one submission packet per directory with unique descriptions and rules citations, and the maintenance ledger.
Files in this package (2)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named developer-discovery-surfaces.

Database snapshot: 13.11.2026 · package version b8903f4f74cb (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

  • 90directory-listings
    Plan white-hat directory and listing submissions that reinforce brand entities (niche directories, associations, app stores, local listings). Use when the user asks for directory submission, listing outreach, citation building for local SEO, or where to list the brand safely.
  • 90plugin-submission
    Govern discovery, eligibility, and submission of a plugin or skill to official directories, registries, marketplaces, and curated GitHub lists. Use when preparing or sending plugin listings, marketplace forms, directory PRs, or repository recommendations; require current policy…
  • 100directory-submission
    When the user wants to submit a product to directories, launch platforms, curated lists, or app stores. Reads project-context.md when present and generates ready-to-paste submission content per platform. Also use when the user mentions "directory submission," "get listed," "app…
  • 100directory-submission
    When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads root contextus.md when present. Also use when the user mentions "directory submission," "get listed," "app store…
  • 90directory-submission
    Run a directory submission batch with a queue, brief, contact, inbox access, assets, duplicate check, submission, verification, and status tracking. Use for launch distribution and citations.
  • 90directory-submission-plan
    Pick the directories and marketplaces worth listing on, and prepare one set of assets that fits all of them. Use when launching a tool, when someone asks where to list a product, or when directory submissions are eating time for no return.

Feedback and reports

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