Menu
Generate placeholder text — paragraphs, lists, code snippets, or markdown stubs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
How to build a NEW tool of your own by writing its code in your sandbox, testing it, and forging it into a live, callable tool with `env(action="forge_tool")`. Use when no existing tool does what you need and you can implement it as a small script. Multiple tools + skills can be saved together as one reusable Sandbox Tool Pack.
How to inspect and edit your OWN operating environment at runtime — system prompt, active tools, and skills — using the `env` tool. Use when you need to change your own capabilities (turn a tool on/off, rewrite your instructions, author a new skill) or save them for this session.
Run the same task on a recurring cron schedule. Parses interval syntax (5m, 2h, 1d, "*/15 * * * *"), records the schedule, and acknowledges back to the user.
Review code in the current working tree across three independent dimensions (reuse, quality, efficiency) and synthesise a small punch-list of high-value cleanups.
Interview the user about a workflow they keep repeating, then generate a reusable SKILL.md and write it to disk so the next session starts with the skill already loaded.
Apply the same prompt or operation to a list of items in turn, collecting results. Useful for "do X to each of these files / PRs / records" tasks.
| name | Lorem Ipsum |
| description | Generate placeholder text — paragraphs, lists, code snippets, or markdown stubs. |
| category | utility |
| effort | low |
| when_to_use | When a draft, mock-up, demo, or test fixture needs filler text. Pick paragraph / list / code style based on the surrounding context. Don't use for real user-facing copy. |
| arguments | ["count","style"] |
| argument_hint | [count=3] [style=paragraph|list|code|markdown] |
| examples | ["3 paragraphs of placeholder text","5-item bullet list with realistic-looking labels","JSON snippet with example fields","Markdown blog post stub with sections"] |
| version | 1.0.0 |
You are generating filler / placeholder text. The user does not want real content — they want something that looks like content so they can wireframe a layout, demo a flow, or fill out a test fixture.
${count} — how many units to produce. Defaults to 3 when the
caller leaves it blank. Interpret "unit" based on the chosen style:
paragraphs, list items, code blocks, etc.${style} — one of:
paragraph (default) — flowing prose, 3–5 sentences each.list — bulleted items, each one short (≤ 12 words).code — code-shaped placeholder. Pick a language that fits the
surrounding context (TS / Python / JSON / SQL); use realistic
identifiers (fetchUserById, users.email) instead of foo.markdown — small markdown block with a heading, a paragraph,
a list, and one code fence.paragraph. If count is missing, default to 3.count units in the chosen style.Plain lorem ipsum text gives away that something is unfinished but
adds no signal about what the finished content will look like.
This skill produces context-aware filler so demos and wireframes
read more like the real thing.