How do I install the Pocdd Create skill?

Run npx skillmds@latest add dailybothq/pocdd-create in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pocdd Create safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pocdd Create?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pocdd Create free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pocdd Create?

dailybothq (@dailybothq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pocdd Create by dailybothq — Agent Skill

Name: Pocdd Create
Author: dailybothq

Pocdd Create

Create a new POC-driven feature file under .pocs/ from any source (a sentence, an issue, a document, a URL). Picks the file format by risk, writes the Goal, and seeds Remaining gaps including a failure-mode sweep. Use for "/poc <SOURCE>" or "start a POC for X".

dailybothq 44e3789 2.6 KB Updated Sep 17, 2026

File contents

POCDD — Create

Bootstrap one self-contained POC file from a SOURCE. First read ../shared/conventions.md.

Configured languages for this install: python,md

Inputs

SOURCE is anything that defines the goal: a one-line sentence, an issue id/link, a path to a document, or a provider URL. (/poc create <SOURCE> and bare /poc <SOURCE> both arrive here.)

Procedure

Gather context from the SOURCE. Read the file, fetch the URL, or read the issue. Distil it into a single Goal statement. If the source is just a sentence, use it verbatim as the goal.
Choose the format by risk (see conventions):
- Unknown external/runtime behavior (API, OAuth, sync, time zones) → runnable file from the templates that match this install:
  - Python: copy ../templates/poc.py
  - Markdown: copy ../templates/poc.md
- Internal/domain complexity (refactor, wiring, product rules) → .md when available in this install.
- When in doubt, prefer the runnable form if there is any external system to probe; otherwise .md.
Name it by domain — short kebab/snake name (e.g. calendar, holidays-sync). Never test.
Resolve and create .pocs/ via ../shared/context.sh (pocdd_ensure_dir).
Write the file from the chosen template into .pocs/<name>.<ext>, filling the Goal section and setting the header phase: spike.
Seed Remaining gaps — the highest-value step. Enumerate what must be proven, decided, or handled to reach the goal. Tag each [agent] or [user], give stable ids G1…. Always run the failure-mode sweep for anything external (auth/token refresh, pagination, rate limits, partial failures, retries/idempotency, malformed data, time zones).
Report: the file path, format chosen (and why), and the seeded gap list split by owner. Suggest /poc work <name> next (at most 2 [agent] gaps close per work pass on this install).

Guardrails

Never write outside .pocs/. Never commit .pocs/.
Reference codebase by path; do not paste production code into the file.
Do not invent product decisions — log them as [user] gaps.

---name: pocdd-createdescription: Create a new POC-driven feature file under .pocs/ from any source (a sentence, an issue, a document, a URL). Picks the file format by risk, writes the Goal, and seeds Remaining gaps including a failure-mode sweep. Use for "/poc <SOURCE>" or "start a POC for X".---# POCDD — CreateBootstrap one self-contained POC file from a **SOURCE**. First read[`../shared/conventions.md`](../shared/conventions.md).Configured languages for this install: **python,md**## Inputs`SOURCE` is anything that defines the goal: a one-line sentence, an issue id/link,a path to a document, or a provider URL. (`/poc create <SOURCE>` and bare`/poc <SOURCE>` both arrive here.)## Procedure1. **Gather context from the SOURCE.** Read the file, fetch the URL, or read the issue. Distil it into a single **Goal** statement. If the source is just a sentence, use it verbatim as the goal.2. **Choose the format by risk** (see conventions): - *Unknown external/runtime behavior* (API, OAuth, sync, time zones) → **runnable** file from the templates that match this install: - Python: copy [`../templates/poc.py`](../templates/poc.py) - Markdown: copy [`../templates/poc.md`](../templates/poc.md) - *Internal/domain complexity* (refactor, wiring, product rules) → **`.md`** when available in this install. - When in doubt, prefer the runnable form if there is *any* external system to probe; otherwise `.md`.3. **Name it by domain** — short `kebab`/`snake` name (e.g. `calendar`, `holidays-sync`). Never `test`.4. **Resolve and create `.pocs/`** via [`../shared/context.sh`](../shared/context.sh) (`pocdd_ensure_dir`).5. **Write the file** from the chosen template into `.pocs/<name>.<ext>`, filling the **Goal** section and setting the header `phase: spike`.6. **Seed Remaining gaps — the highest-value step.** Enumerate what must be *proven*, *decided*, or *handled* to reach the goal. Tag each `[agent]` or `[user]`, give stable ids `G1…`. **Always run the failure-mode sweep** for anything external (auth/token refresh, pagination, rate limits, partial failures, retries/idempotency, malformed data, time zones).7. **Report**: the file path, format chosen (and why), and the seeded gap list split by owner. Suggest `/poc work <name>` next (at most **2** `[agent]` gaps close per work pass on this install).## Guardrails- Never write outside `.pocs/`. Never commit `.pocs/`.- Reference codebase by path; do not paste production code into the file.- Do not invent product decisions — log them as `[user]` gaps.

Frequently asked questions