outline

Tinjau · 68
Diindeks di Registry

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
Star28
Versi1.0.0
Kualitas61/100 · Menjanjikan
Kepercayaan68/100 · Hanya sandbox
Audit78/100 · Perlu ditinjau

Profil aset

Riset dan pekerjaan pengetahuan

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

Lihat kategori

Skenario

Agent riset

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

Kecocokan Agent

Claude Code + CLI + Codex

Cocok untuk Codex, Claude Code, Cursor, CLI, atau Agent khusus.

Pasang

Siap

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

Pemeliharaan

Terkini

3 hari sejak push

Risiko

Perlu ditinjau

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.

Kualitas GitHub

28

61/100 Kualitas · 76/100 Kepercayaan

Tag cakupan

RisetAgent risetagent-skill

Catatan ulasan

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

Kartu adopsi Agent

Kepercayaan, audit, dan kesiapan pemasangan dalam sekali lihat

Skor ini menggabungkan metadata repositori publik, sinyal ulasan OpenAgentSkill, kebaruan pemeliharaan, dan kesiapan pemasangan. Ini adalah sinyal shortlist, bukan pengganti peninjauan manusia.

Kualitas

Menjanjikan
61

Useful candidate, but compare it with alternatives before adopting.

Kepercayaan

Hanya sandbox
68

Kandidat berguna dengan sinyal kepercayaan yang kurang atau bercampur. Gunakan di ruang kerja terisolasi hingga loop hasil membuktikan kecocokan tugas.

Audit

Perlu ditinjau
78

Tinjauan yang dapat dibaca mesin tentang kesiapan pemasangan, metadata keamanan, pemeliharaan, dan risiko adopsi.

Trust Score OpenAgentSkill v5

Tinjauan manusia sebelum pemasangan

Jalankan hanya dalam sandbox dan bandingkan alternatif terdekat sebelum digunakan untuk kerja nyata.

CodexClaude CodeCursorOpenAgentSkill CLI

Star

28 star GitHub

Aktivitas repositori

28 star dan 5 fork

Pemeliharaan

3 hari sejak push

Lisensi

MIT

Pasang

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

Keamanan pemasangan

Jalur pemasangan paket atau runtime standar

Cakupan izin

Tidak ada cakupan izin berisiko tinggi dalam metadata publik

Hasil Agent

Belum ada data hasil Agent

Dokumentasi

Konteks README/SKILL.md kuat

Ringkasan risiko

Tinjau sebelum produksi

  • 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

Kesiapan pemasangan

Jalur pemasangan tersedia

  • Jalur pemasangan tersedia
  • Bukti repositori tersedia
  • Lisensi dinyatakan
  • Belum ada bukti hasil Agent-Proven

Metadata yang dapat dibaca Agent

Data keputusan yang dapat dibaca mesin untuk skill ini.

Gunakan blok ini atau JSON tersemat untuk memutuskan apakah Agent perlu memasang skill ini, memilih alternatif, atau meminta tinjauan manusia terlebih dahulu.

Buka JSON

Tugas yang sesuai

  • Alur kerja Agent riset
  • Tim Claude Code
  • builders willing to evaluate younger projects
  • Sumber pencarian

Agent yang sesuai

CodexClaude CodeCursorOpenAgentSkill CLICLI

Keputusan pemasangan

Perintah
npx skills add Deupaxx/EveryDay-Writer --skill outline
Kebijakan
Tinjau
Tinjauan manusia
Ya

Kepercayaan dan risiko

Kepercayaan
68/100
Audit
78/100
Tingkat risiko
Perlu ditinjau

Lingkar hasil

Endpoint
/api/agent/outcome
ID event
resolve
Hasil
5

Perintah pemasangan

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

Jangan gunakan ketika

  • Tim yang membutuhkan SLA dengan dukungan vendor
  • 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

Keamanan Agent v2

62/100 · Tinjau sebelum memasang

Ditinjau dengan catatan izinTinjau

Kandidat yang dapat digunakan, tetapi Agent harus menampilkan catatan izin dan audit sebelum memasang.

Memerlukan persetujuan manusia sebelum memasang ke workspace nyata.

Selesaikan via API

Sedang

Akses jaringan

Skill kemungkinan mengambil halaman jarak jauh, API, repositori, atau layanan eksternal.

Sedang

Akses sistem file

Skill dapat membaca atau menulis file proyek, dokumen, artefak yang dihasilkan, atau status workspace lokal.

  • 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.

Target pemasangan

Pasang skill ini di alur Agent Anda

Gunakan endpoint publik untuk mengambil perintah, checklist keamanan, prompt target, dan tautan kanonis.

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

Rencana resolusi Agent

Biarkan Agent memverifikasi kecocokan sebelum memasang.

API Resolve mengembalikan skill utama, alternatif, kebijakan keamanan, catatan audit, target pemasangan, dan prompt siap pakai.

Buka rencana teks

Agent harus memeriksa

  • 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.

Salin 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.

Serah-terima Agent

Berikan jalur pemasangan kepada Agent, bukan direktori lain.

Gunakan endpoint publik untuk mengambil perintah, checklist keamanan, prompt target, dan tautan kanonis.

Buka API pemasangan

Prompt Agent

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

Metadata Registry

Profil yang dapat dibaca Agent untuk pemilihan skill otomatis.

API Registry menyediakan sinyal keputusan, kepercayaan, audit, use case, dan pemasangan tanpa mengikis UI.

Buka Manifest

Kecocokan Agent

61/100

Agent riset

Platform

Claude Code

Laporan audit

Perlu ditinjau · 78/100

Tinjauan yang dapat dibaca mesin tentang kesiapan pemasangan, metadata keamanan, pemeliharaan, dan risiko adopsi.

Lihat laporan auditLihat laporan evaluasi

Panel keputusan Agent

Fallback candidate for Research agents

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

61
Kesiapan
Prototipe
Tahap

Peran di stack

Kandidat cadangan

Kecocokan utama

Agent riset

Label kepercayaan

Buat prototipe dulu

Jalur pemasangan

Perintah siap

Gunakan saat

  • Alur kerja Agent riset
  • Tim Claude Code
  • builders willing to evaluate younger projects

Bukti

  • recent repository activity
  • install command or GitHub repo available
  • profil kualitas 61/100
  • 2 event interaksi OpenAgentSkill

tinjau dulu

  • 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.

Jalur implementasi

  1. 1Pasang di Agent sandbox dan jalankan satu tugas Agent riset dari awal hingga akhir.
  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.

Profil kepercayaan

Hanya sandbox

Kandidat berguna dengan sinyal kepercayaan yang kurang atau bercampur. Gunakan di ruang kerja terisolasi hingga loop hasil membuktikan kecocokan tugas.

68
Trust Score OpenAgentSkill

Adopsi GitHub

Periksa

28 star GitHub

Aktivitas star/fork

Periksa

28 star dan 5 fork; aktivitas issue tidak tersedia dalam metadata saat ini

Pemeliharaan terbaru

Lulus

3 hari sejak push

Kejelasan lisensi

Lulus

MIT

Sinyal positif

  • Tinjauan AI disetujui
  • Jalur pemasangan tersedia
  • Bukti repositori tersedia
  • Repositori yang baru dipelihara
  • Perintah pemasangan tidak memiliki pola berisiko tinggi yang jelas
  • Loop hasil siap tetapi membutuhkan eksekusi Agent nyata pertama

Tinjau sebelum memasang

  • 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
  • Belum ada laporan hasil Agent nyata
  • Tinjauan manusia diperlukan sebelum pemasangan tanpa pengawasan

Tindakan yang disarankan

Jalankan hanya dalam sandbox dan bandingkan alternatif terdekat sebelum digunakan untuk kerja nyata.

Profil kualitas

Menjanjikan kandidat untuk alur kerja Agent

Useful candidate, but compare it with alternatives before adopting.

61
Star GitHub
28
Keterkinian
3 hari lalu
Siap dipasang
Ya
Lisensi
MIT
Tinjau sebelum memasang: 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.

Kecocokan alur kerja

Gunakan skill ini pada skenario berikut

Kecocokan alur kerja

Tambahkan ke alur kerja lengkap

Daftar alternatif

Bandingkan sebelum memasang

Similar skills that may fit this task.

Bandingkan semua

Ringkasan

--- 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

Detail teknis

Versi
1.0.0
Lisensi
MIT
Pembaruan terakhir
20 Agu 2026
Diterbitkan
20 Agu 2026

Ringkasan keputusan

Kandidat cadangan

61
Siap
Prototipe
Tahap

recent repository activity

Audit

Tinjauan pemasangan

Tinjauan pemasangan dan adopsi

78
Perlu ditinjau
Keamanan
82/100
Pemeliharaan
100/100
Pasang
92/100
Buka audit lengkapLihat laporan evaluasi

Bukti tervalidasi Agent

Bukti tervalidasi Agent

Laporan hasil setelah resolve, tinjau, pasang, dan satu eksekusi terbatas.

0
Terbukti
Needs first agent runPasang otomatis: tinjau duluTerakhir: Tidak diketahui
Tingkat sukses
Kegagalan terbaru
Hasil
0
Kualitas output
Gagal
0
Tidak relevan
0
Pemasangan
0
Diblokir risiko
0
Perlu penyiapan
0
Produksi
0

Belum ada data hasil Agent. Eksekusi pertama dapat melaporkan keberhasilan, kebutuhan setup, blok risiko, kegagalan, atau tidak relevan melalui /api/agent/outcome.

Pasang

Tambahkan ke alur Agent

Gratis dan sumber terbuka. Tinjau laporan sebelum memasang pada Agent produksi.

Siklus pertumbuhan

Kit berbagi

X

Draf berbasis skenario untuk outline, siap untuk posting manual di X.

Catatan kurator
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
Buka draf X
Balasan opsional dengan perintah pemasangan
Listing + install path for outline:
https://www.openagentskill.com/skills/deupaxx-outline?ref=x

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

Sumber listing

Diindeks Registry

Dapat diklaim

Listing ini diindeks dari sumber publik dan belum ditandai resmi hingga klaim pemelihara disetujui.

Kreator
Deupaxx
Diindeks oleh
Indeks komunitas OpenAgentSkill

Atribusi menautkan ke repositori publik atau profil kreator. Kreator dapat mengklaim listing untuk memperbarui sinyal kepemilikan.

Klaim skill ini

Klaim pemilik

Klaim listing skill ini

Listing Diindeks Registry ini dikaitkan dengan Deupaxx, tetapi belum ditandai resmi. Klaim untuk menambahkan sinyal pemilik terverifikasi dan membuat pembaruan peluncuran, pemasangan, serta audit berikutnya lebih tepercaya.

Kit backlink kreator

Tambahkan badge bukti ke README Anda

Tampilkan listing kanonis, sinyal kepercayaan dan audit saat ini, serta bukti Agent-Proven nyata di tempat pengembang mengevaluasi repositori.

[![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)

Penulis

D

Deupaxx

@deupaxx

Kecocokan platform

Sinyal kesehatan

Star GitHub
28
Skor kualitas
34/100
Push GitHub terakhir
20 Agu 2026
Petunjuk framework
Tidak diketahui
Tampilan OpenAgentSkill
2
Salinan pemasangan
0
Klik keluar
0

Sinyal komunitas

Bagikan apakah skill ini bermanfaat untuk alur kerja Agent Anda. Masukan gabungan meningkatkan peringkat dari waktu ke waktu.

Kepercayaan & keamanan

Hanya sandbox

68
  • Adopsi GitHub28 star GitHubPeriksa
  • Aktivitas star/fork28 star dan 5 fork; aktivitas issue tidak tersedia dalam metadata saat iniPeriksa
  • Pemeliharaan terbaru3 hari sejak pushLulus
  • Kejelasan lisensiMITLulus
  • Kelengkapan README/SKILL.mdMetadata memuat konteks penggunaan dan alur kerja yang cukupLulus
  • Risiko dependensi/runtimeTidak ada petunjuk risiko dependensi besar dalam metadata publikLulus