Skip to content
Marketing

Onboarding CRO

coreyhaines31

Optimize onboarding around first useful value with minimal necessary setup.

SKILL.md

---
name: knoveya-onboarding-cro
description: "Optimize onboarding around first useful value with minimal necessary setup. Use for matching marketing work."
---

# Onboarding CRO

## Scope

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

## Workflow

Optimize onboarding around first useful value with minimal necessary setup.

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

The flow preserves recovery and does not add questions without a task-related purpose.

## Example task

Let a new user try a sample before importing private data.

## 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-onboarding-cro as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-onboarding-cro/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

Let a new user try a sample before importing private data.

Verify

The flow preserves recovery and does not add questions without a task-related purpose.

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.