Skip to content
Marketing

Directory Submissions

coreyhaines31

Prepare directory submissions from accurate positioning and a prioritized audience-fit list.

SKILL.md

---
name: knoveya-directory-submissions
description: "Prepare directory submissions from accurate positioning and a prioritized audience-fit list. Use for matching marketing work."
---

# Directory Submissions

## Scope

Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.

## Workflow

Prepare directory submissions from accurate positioning and a prioritized audience-fit list.

Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.

## Acceptance check

No account creation, payment, or public submission occurs without authorization.

## Example task

Draft consistent product descriptions for review before submitting.

## Report

State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.

How to use

Copy the full block, including its frontmatter, into a new folder named knoveya-directory-submissions as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-directory-submissions/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.

This is an independent Knoveya skill. No files are installed by this website.

Example

Draft consistent product descriptions for review before submitting.

Verify

No account creation, payment, or public submission occurs without authorization.

Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.

Limits

The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.