outline

REVIEW · 68
Registry indexed

Turn a vague idea into a tight, format-specific outline through structured interrogation. Use when the user is stuck on structure, does not know what to write, or has a topic but no angle. Works for newsletters, sales pages, posts, scenes, and scripts.

Verified installs0
Stars28
Version1.0.0
Quality61/100 · Promising
Trust68/100 · Sandbox only
Audit78/100 · Needs review

Supply asset profile

Research and knowledge work

Deep research, source comparison, literature review, RAG, knowledge search, and reports.

Browse track

Scenario

Research agents

I need my agent to research a topic, compare sources, and produce a concise report.

Agent fit

Claude Code + CLI + Codex

Codex, Claude Code, Cursor, CLI, or custom agents.

Install

Ready

npx skills add Deupaxx/EveryDay-Writer --skill outline

Maintenance

fresh

3d since push

Risk

Needs review

The skill depends on external files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory. This may cause failures if the skill is used outside the full repository context.

GitHub quality

28

61/100 Quality · 76/100 Trust

Coverage tags

ResearchResearch agentsagent-skill

Review notes

The skill depends on external files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory. This may cause failures if the skill is used outside the full repository context. · Low GitHub adoption signal

Agent adoption scorecard

Trust, audit, and install readiness at a glance

These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.

Quality

Promising
61

Useful candidate, but compare it with alternatives before adopting.

Trust

Sandbox only
68

Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.

Audit

Needs review
78

A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.

OpenAgentSkill Trust Score v5

Human review before install

Run only in a sandbox and compare close alternatives before using it for real work.

CodexClaude CodeCursorOpenAgentSkill CLI

Stars

28 GitHub stars

Repo activity

28 stars, 5 forks

Maintenance

3d since push

License

MIT

Install

npx skills add Deupaxx/EveryDay-Writer --skill outline

Install safety

standard package or runtime install path

Permission surface

no high-risk permission surface in public metadata

Agent outcomes

No agent outcome data yet

Docs

Strong README/SKILL.md context

Risk summary

Review before production

  • The skill depends on external files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory. This may cause failures if the skill is used outside the full repository context.
  • Low GitHub adoption signal
  • Quality score needs review
  • GitHub adoption: 28 GitHub stars

Install readiness

Install path available

  • Install path is available
  • Repository evidence is available
  • License is declared
  • No Agent Proven outcome evidence yet

Agent-readable metadata

Machine-readable decision data for this skill.

Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.

Open JSON

Suited tasks

  • Research agents workflows
  • Claude Code teams
  • builders willing to evaluate younger projects
  • Search sources

Suited agents

CodexClaude CodeCursorOpenAgentSkill CLICLI

Install decision

Command
npx skills add Deupaxx/EveryDay-Writer --skill outline
Policy
review
Human review
yes

Trust and risk

Trust
68/100
Audit
78/100
Risk level
Needs review

Outcome loop

Endpoint
/api/agent/outcome
Event ID
resolve
Outcomes
5

Install command

npx skills add Deupaxx/EveryDay-Writer --skill outline

Do not use when

  • teams that need a vendor-supported SLA
  • production agents without a repository review
  • Low GitHub adoption signal
  • The skill depends on external files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory. This may cause failures if the skill is used outside the full repository context.
  • Quality score needs review

Agent safety v2

62/100 · Review before install

Reviewed with permission notesreview

Usable candidate, but the agent should surface permission and audit notes before installation.

Require human approval before installing into a real workspace.

Resolve via API

medium

Network access

Skill likely fetches remote pages, APIs, repositories, or external services.

medium

Filesystem access

Skill may read or write project files, documents, generated artifacts, or local workspace state.

  • The skill depends on external files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory. This may cause failures if the skill is used outside the full repository context.

Install targets

Install this skill in your agent workflow

Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.

skill install

OpenAgentSkill CLI

Resolve policy, run the source installer safely, and report a verified install receipt.

$ npx --yes https://github.com/Leon-Drq/openagentskill/releases/download/cli-v0.2.1/openagentskill-0.2.1.tgz install deupaxx-outline

Agent resolve plan

Let an agent verify fit before installing.

The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.

Open text plan

Agent should check

  • Task fit and alternatives from Resolve API.
  • Audit score, trust score, and safety policy warnings.
  • Install target compatibility for Codex, Claude Code, Cursor, or CLI.

Copy prompt

Task: Use outline in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20outline%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/deupaxx-outline/install
Install command: npx skills add Deupaxx/EveryDay-Writer --skill outline
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.

Agent handoff

Give an agent the install path, not another directory page.

Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.

Open install API

Agent prompt

Use outline for this task. Review https://www.openagentskill.com/api/skills/deupaxx-outline/install, then install with: npx skills add Deupaxx/EveryDay-Writer --skill outline

Registry metadata

Agent-readable profile for automatic skill selection.

This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.

Open manifest

Agent fit

61/100

Research agents

Platforms

Claude Code

Audit report

Needs review · 78/100

A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.

View audit reportView eval report

Agent decision cockpit

Fallback candidate for Research agents

Prototype with this skill first; keep a fallback candidate ready.

61
Readiness
Prototype
Stage

Role in stack

Fallback candidate

Primary fit

Research agents

Trust label

Prototype first

Install path

Command ready

Use when

  • Research agents workflows
  • Claude Code teams
  • builders willing to evaluate younger projects

Evidence

  • recent repository activity
  • install command or GitHub repo available
  • 61/100 quality profile
  • 2 OpenAgentSkill engagement events

review first

  • Low GitHub adoption signal
  • The skill depends on external files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory. This may cause failures if the skill is used outside the full repository context.

Implementation path

  1. 1Install it in a sandbox agent and run one Research agents task end to end.
  2. 2Compare output quality, latency, and failure behavior against at least one alternative.
  3. 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.

Trust profile

Sandbox only

Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.

68
OpenAgentSkill Trust Score

GitHub adoption

CHECK

28 GitHub stars

Stars/forks activity

CHECK

28 stars, 5 forks; issue activity unavailable in current metadata

Recent maintenance

PASS

3d since push

License clarity

PASS

MIT

Good signals

  • AI review approved
  • Install path is available
  • Repository evidence is available
  • Recently maintained repository
  • Install command has no obvious high-risk pattern
  • Outcome loop is ready but needs first real agent run

Review before install

  • The skill depends on external files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory. This may cause failures if the skill is used outside the full repository context.
  • Low GitHub adoption signal
  • Quality score needs review
  • GitHub adoption: 28 GitHub stars
  • Stars/forks activity: 28 stars, 5 forks; issue activity unavailable in current metadata
  • No real agent outcome reports yet
  • Human review required before unattended installation

Recommended action

Run only in a sandbox and compare close alternatives before using it for real work.

Quality profile

Promising candidate for agent workflows

Useful candidate, but compare it with alternatives before adopting.

61
GitHub stars
28
Freshness
3d ago
Install ready
Yes
License
MIT
Review before install: Low GitHub adoption signal · The skill depends on external files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory. This may cause failures if the skill is used outside the full repository context.

Workflow fit

Use this skill in these scenarios

Workflow fit

Add it to a complete workflow

Alternative shortlist

Compare before you install

Similar skills that may fit this task.

Compare all

Overview

--- name: outline description: | Turn a vague idea into a tight, format-specific outline through structured interrogation. Use when the user is stuck on structure, does not know what to write, or has a topic but no angle. Works for newsletters, sales pages, posts, scenes, and scripts. license: MIT metadata: version: "0.3.0" ---

# EW Skill — Idea-to-Outline Engine

**Dependency chain. Read these in order before writing anything:**

1. `core/anti-ai-rules.md` (read fully; Section 0 sets the standard, 0.1 sets precedence, 0.2 forbids fabrication, 9 and 10 stop over-correction) 2. `core/ai_slop_commandments.md` (mechanism reference and diagnostic checklist) 3. `core/voice-profile.md` (this writer's voice fingerprint; if `Completed: No`, stop and run onboarding) 4. Any `.md` files the user has dropped in `references/`

This chain applies on direct invocation (`/ew:outline`) exactly as it does on dispatch through `/ew`. Direct invocation skips routing, not constraints.

---

## WHAT THIS SKILL IS FOR

A structured interrogation that takes a vague idea and produces a tight outline before a single word of prose is written. Writers don't just struggle with writing — they struggle with starting, because they don't know what they're actually trying to say.

This skill fixes that. The interrogation is short. The outline is specific. When the outline is done, the writer knows what every section is for and what it must accomplish.

A newsletter outline looks nothing like a sales page outline. This skill generates format-specific outlines.

---

## THE INTERROGATION PROCESS

### Phase 1: Identify the format

If the user hasn't specified a format, ask:

> "What format is this — newsletter, sales page, LinkedIn post, tweet thread, short story, screenplay, or something else?"

Wait for the answer before proceeding. Do not guess the format from the idea.

### Phase 2: Identify the core claim

Ask this question, one question only:

> "What's the one thing you want the reader to walk away knowing or feeling? Not the topic — the point."

This is the hardest question in writing. If the user can't answer it, the idea isn't ready to outline. If they give a vague answer ("I want them to feel inspired"), press once: "Inspired to do what, specifically?"

The answer to this question is the spine of the outline. Every section must serve it.

### Phase 3: Format-specific interrogation

Run the question set for the identified format. Ask one question at a time. Do not ask all questions at once.

---

#### NEWSLETTER (creative/story-led)

1. "What's the ordinary world — what's the situation before the thing you're about to describe happened?" 2. "What's the inciting incident — the specific event or moment that made the ordinary world impossible to go back to?" 3. "What did you try that didn't work, or what's the conventional wisdom that gets this wrong?" 4. "What's the key insight — the thing you now know that you didn't know before, stated in one sentence?" 5. "What does the new equilibrium look like — what's true now that wasn't true before?"

Skip any question the user has already answered in their idea description. Don't ask for information you have.

---

#### NEWSLETTER (technical/analytical)

1. "What's the problem — stated as specifically as possible, not as a category but as a concrete instance?" 2. "What's the key insight that most people get wrong or don't know?" 3. "What's the evidence or mechanism that proves the insight — data, example, analogy?" 4. "What should the reader do or think differently after reading this?"

---

#### SALES PAGE

1. "Who is this for — describe the specific person, not a demographic. What are they doing right now that this product replaces or improves?" 2. "What have they already tried that didn't work? What makes those attempts fail?" 3. "What is the mechanism — why does this work where other solutions don't? One sentence." 4. "What does life look like after — specific outcome, not transformation language." 5. "What's the main objection the buyer will have at the moment they're about to click buy?"

---

#### LINKEDIN POST

1. "What's the hook — the one observation, counterintuitive claim, or specific scene that makes someone stop scrolling?" 2. "What's the turn — where does the post change direction or reveal the point?" 3. "What do you want the reader to take from this — an action, a reframe, a question?"

---

#### TWEET / X THREAD

Single tweet: 1. "State the idea in one sentence. Don't explain it — state it." 2. "What's the sharpest version of that sentence — fewer words, stronger verb?"

Thread: 1. "What's the full claim — what are you arguing across the whole thread?" 2. "What are the 3–5 distinct points that build the argument? Each one should advance, not restate." 3. "What's the last tweet — the sharpest thing you have, the thing the reader should screenshot?"

---

#### SHORT STORY / FICTION SCENE

1. "What does the POV character want in this scene — the surface want, stated as an action they take?" 2. "What force opposes that want — a person, a circumstance, or an internal conflict?" 3. "What changes between the opening and the closing of the scene — knowledge, position, relationship, or understanding?" 4. "What's the last beat — the image or line the scene ends on?"

---

#### SCREENPLAY / SCRIPT

1. "What is the protagonist's external goal — what are they actively pursuing?" 2. "What is their internal need — what do they actually require that they can't name yet?" 3. "What is the inciting incident — the specific event that makes the ordinary world impossible to continue?" 4. "What is the protagonist's darkest moment — the point where they have lost or believe they have?" 5. "How does the protagonist resolve the story — through an active choice, not a rescue?"

---

### Phase 4: Generate the outline

Once all relevant questions are answered, produce the outline. Format:

---

**[TITLE PLACEHOLDER — working title or description of what it's about]**

**Core claim:** [The one-sentence answer from Phase 2]

**Format:** [Newsletter / Sales page / LinkedIn / etc.]

**Outline:**

[Section name — what this section accomplishes in the piece] - [Specific content: what goes here, stated as precisely as possible] - [Key line or image if identified during the interrogation]

[Section name] - [Specific content] - [Key line or image]

[Continue for each section]

**The stakes:** [One sentence on what the reader gains if they read to the end — the payoff contract]

**What to write first:** [The single hardest or most important section — start here, not at the beginning]

---

## WHAT THIS SKILL DOES NOT DO

- Does not write the piece — the outline is the output - Does not ask more questions than necessary — if the user's idea already answers a question, skip it - Does not produce generic outlines that could apply to any piece on this topic — the outline must be specific to this writer's idea and voice

---

## POST-OUTLINE CHECK

Before presenting the outline, verify: - [ ] The core claim is specific enough that only this piece could fulfill it - [ ] Every section serves the core claim — no section exists just because this format "usually has" that section - [ ] The "What to write first" recommendation is genuinely the hardest or most generative section, not just section 1 - [ ] The outline is tight enough that the writer can start immediately — no more interrogation needed

Technical details

Version
1.0.0
License
MIT
Last updated
Aug 20, 2026
Published
Aug 20, 2026

Decision snapshot

Fallback candidate

61
Ready
Prototype
Stage

recent repository activity

Audit

Install review

Install and adoption review

78
Needs review
Security
82/100
Maintenance
100/100
Install
92/100
Open full auditView eval report

Agent-proven evidence

Agent-proven evidence

Outcome reports after resolve, review, install, and one narrow run.

0
Proven
Needs first agent runAuto-install: review firstLast: Unknown
Success rate
Recent failure
Outcomes
0
Output quality
Failed
0
Not relevant
0
Installs
0
Risk blocked
0
Setup needed
0
Production
0

No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.

Install

Add to agent workflow

Free and open source. Review the report before installing into production agents.

Growth loop

Share kit

X

Scenario-led draft for outline, ready for a manual X post.

Curator note
A practical pick for a web workflow:

outline: Turn a vague idea into a tight, format-specific outline through structured interrogation. Use when the user is stuck on str...

28 stars

https://www.openagentskill.com/skills/deupaxx-outline?ref=x
Open X draft
Optional reply with install command
Listing + install path for outline:
https://www.openagentskill.com/skills/deupaxx-outline?ref=x

Install: npx skills add Deupaxx/EveryDay-Writer --skill outline

Listing source

Registry indexed

Claimable

This listing was indexed from public sources and is not marked official until a maintainer claim is approved.

Creator
Deupaxx
Indexed by
OpenAgentSkill community index

Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.

Claim this skill

Owner claim

Claim this skill listing

This Registry indexed listing is attributed to Deupaxx but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.

Creator backlink kit

Add the evidence badges to your README

Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.

[![Listed on OpenAgentSkill](https://www.openagentskill.com/api/badge/deupaxx-outline?metric=listed&label=Listed)](https://www.openagentskill.com/skills/deupaxx-outline)
[![OpenAgentSkill Trust](https://www.openagentskill.com/api/badge/deupaxx-outline?metric=trust&label=Trust)](https://www.openagentskill.com/skills/deupaxx-outline)
[![OpenAgentSkill Audit](https://www.openagentskill.com/api/badge/deupaxx-outline?metric=audit&label=Audit)](https://www.openagentskill.com/skills/deupaxx-outline/audit)
[![Agent Proven](https://www.openagentskill.com/api/badge/deupaxx-outline?metric=proven&label=Agent%20Proven)](https://www.openagentskill.com/skills/deupaxx-outline)

Author

D

Deupaxx

@deupaxx

Platform fit

Health signals

GitHub stars
28
Quality score
34/100
Last GitHub push
Aug 20, 2026
Framework hints
Unknown
OpenAgentSkill views
2
Install copies
0
Outbound clicks
0

Community signal

Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.

Trust & safety

Sandbox only

68
  • GitHub adoption28 GitHub starsCHECK
  • Stars/forks activity28 stars, 5 forks; issue activity unavailable in current metadataCHECK
  • Recent maintenance3d since pushPASS
  • License clarityMITPASS
  • README/SKILL.md completenessMetadata includes enough usage and workflow contextPASS
  • Dependency/runtime riskno major dependency risk hints in public metadataPASS