inkos-multi-agent-novel-writing▌
aradotso/trending-skills · updated May 29, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Skill by ara.so — Daily 2026 Skills collection
InkOS Multi-Agent Novel Writing
Skill by ara.so — Daily 2026 Skills collection
InkOS is a multi-agent CLI system that autonomously writes, audits, and revises novels. Agents handle the full pipeline: Writer → Validator → Auditor → Reviser, with human review gates at configurable checkpoints.
Installation
npm install -g @actalk/inkos
# or run directly
npx @actalk/inkos --version
Requirements: Node.js ≥ 20.0.0
Quick Start
# Create a new novel project
inkos book create --title "吞天魔帝" --genre xuanhuan
# Write the next chapter
inkos write next 吞天魔帝
# Audit a specific chapter
inkos audit 吞天魔帝 --chapter 3
# Run the full daemon (continuous production)
inkos daemon start
Project Structure
After inkos book create, the project directory contains:
story/
outline.md # Story outline (architect agent input)
book_rules.md # Per-book custom rules and audit dimensions
chapter_summaries.md # Auto-generated per-chapter summaries
subplot_board.md # Subplot progress tracking (A/B/C lines)
emotional_arcs.md # Per-character emotional arc tracking
character_matrix.md # Character interaction matrix + info boundaries
parent_canon.md # Spinoff only: imported canon constraints
style_profile.json # Style fingerprint (if style import used)
style_guide.md # LLM-generated qualitative style guide
chapters/
ch001.md
ch002.md
...
Core Commands
Book Management
inkos book create --title "Title" --genre xuanhuan # genres: xuanhuan | xianxia | dushi | horror | general
inkos book list
inkos book status 吞天魔帝
Writing Pipeline
inkos write next 吞天魔帝 # Write next chapter (auto-loads all context)
inkos write chapter 吞天魔帝 5 # Write specific chapter
inkos audit 吞天魔帝 --chapter 3 # Audit chapter (33 dimensions)
inkos revise 吞天魔帝 --chapter 3 # Revise based on audit results
inkos revise 吞天魔帝 --chapter 3 --mode spot-fix # Point fix only (default)
inkos revise 吞天魔帝 --chapter 3 --mode rewrite # Full rewrite (use cautiously)
inkos revise 吞天魔帝 --chapter 3 --mode polish # Polish (no structural changes)
Genre System
inkos genre list # List all built-in genres
inkos genre show xuanhuan # View full rules for a genre
inkos genre copy xuanhuan # Copy genre rules to project for customization
inkos genre create wuxia --name 武侠 # Create new genre from scratch
Style Matching
inkos style analyze reference.txt # Analyze style fingerprint
inkos style import reference.txt 吞天魔帝 # Import style into book
inkos style import reference.txt 吞天魔帝 --name "某作者"
Spinoff (Prequel/Sequel/IF-branch)
inkos book create --title "烈焰前传" --genre xuanhuan
inkos import canon 烈焰前传 --from 吞天魔帝 # Import parent canon constraints
inkos write next 烈焰前传 # Writer auto-reads canon constraints
AIGC Detection
inkos detect 吞天魔帝 --chapter 3 # Detect AIGC markers in chapter
inkos detect 吞天魔帝 --all # Detect all chapters
inkos detect --stats # View detection history statistics
Daemon (Continuous Production)
inkos daemon start # Start scheduler (default: 15 min/cycle)
inkos daemon stop
inkos daemon status
Configuration
Global Config (~/.inkos/config.json)
{
"llm": {
"provider": "openai",
"model": "gpt-4o",
"apiKey": "sk-...",
"temperature": 0.8
},
"daemon": {
"intervalMinutes": 15,
"dailyChapterLimit": 10,
"parallelBooks": 2
},
"webhook": {
"url": "https://your-server.com/hooks/inkos",
"secret": "your-hmac-secret",
"events": ["chapter-complete", "audit-failed", "pipeline-error"]
},
"aigcDetection": {
"provider": "gptzero",
"apiKey": "...",
"endpoint": "https://api.gptzero.me/v2/predict/text"
}
}
Per-Book Rules (story/book_rules.md)
# Book Rules: 吞天魔帝
## 禁忌 (Forbidden)
- 主角不得主动求饶
- 不得出现「命运」「天意」等宿命论表述
## 高疲劳词
- 震撼, 惊骇, 恐惧, 颤抖
## additionalAuditDimensions
- 数值系统一致性: 战力数值不得前后矛盾
- 角色成长节奏: 主角突破间隔不少于3章
## 写手特别指令
- 战斗场面优先感官描写,禁止数值报告
Agent Architecture
InkOS runs five specialized agents in sequence:
ArchitectAgent → outline.md, book_rules.md
↓
WriterAgent → ch00N.md (reads: outline, summaries, arcs, matrix, style_guide, canon)
↓
ValidatorAgent → 11 deterministic rules, zero LLM cost
↓ (error found → trigger spot-fix immediately)
AuditorAgent → 33 LLM dimensions, temperature=0 for consistency
↓
ReviserAgent → spot-fix | rewrite | polish | anti-detect
Post-Write Validator Rules (Deterministic, No LLM)
| Rule | Condition |
|---|---|
| Forbidden patterns | 不是……而是…… constructs |
| Em-dash ban | —— character |
| Transition word density | 仿佛/忽然/竟然≤1 per 3000 chars |
| High-fatigue words | Per-book list, ≤1 per chapter |
| Meta-narrative | Screenwriter-style narration |
| Report terminology | Analytical framework terms in prose |
| Author moralizing | 显然/不言而喻 etc. |
| Collective reaction | 「全场震惊」clichés |
| Consecutive 了 | ≥4 consecutive sentences with 了 |
| Paragraph length | ≥2 paragraphs over 300 chars |
| Book-specific bans | book_rules.md forbidden list |
Audit Dimensions (33 total, LLM-evaluated)
Key dimensions include:
- Dims 1–23: Core narrative quality (plot, character, pacing, foreshadowing)
- Dim 24–26: Subplot stagnation, arc flatness, rhythm monotony (all 5 genres)
- Dim 27: Sensitive content
- Dim 28–31: Spinoff-specific (canon conflicts, future info leakage, world rule consistency, foreshadowing isolation)
- Dim 32: Reader expectation management
- Dim 33: Outline deviation detection
Code Integration Examples
Programmatic Usage (TypeScript)
import { BookManager } from '@actalk/inkos'
import { WriterAgent } from '@actalk/inkos/agents'
import { ValidatorAgent } from '@actalk/inkos/agents'
// Create and configure a book
const manager = new BookManager()
const book = await manager.createBook({
title: '吞天魔帝',
genre: 'xuanhuan',
outlinePath: './my-outline.md'
})
// Run the write pipeline for next chapter
const writer = new WriterAgent({ temperature: 0.8 })
const chapter = await writer.writeNext(book)
// Run deterministic validation (no LLM cost)
const validator = new ValidatorAgent()
const validationResult = await validator.validate(chapter, book)
if (validationResult.hasErrors) {
// Auto spot-fix triggered
const reviser = new ReviserAgent({ mode: 'spot-fix' })
const fixed = await reviser.revise(chapter, validationResult.errors, book)
console.log('Fixed violations:', validationResult.errors.length)
}
Webhook Handler (Express)
import express from 'express'
import crypto from 'crypto'
const app = express()
app.use(express.raw({ type: 'application/json' }))
app.post('/hooks/inkos'How to use inkos-multi-agent-novel-writing on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add inkos-multi-agent-novel-writing
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches inkos-multi-agent-novel-writing from GitHub repository aradotso/trending-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate inkos-multi-agent-novel-writing. Access the skill through slash commands (e.g., /inkos-multi-agent-novel-writing) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★31 reviews- ★★★★★Dhruvi Jain· Dec 28, 2024
inkos-multi-agent-novel-writing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Hana Gonzalez· Dec 4, 2024
Solid pick for teams standardizing on skills: inkos-multi-agent-novel-writing is focused, and the summary matches what you get after install.
- ★★★★★Oshnikdeep· Nov 19, 2024
Useful defaults in inkos-multi-agent-novel-writing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ganesh Mohane· Oct 10, 2024
Registry listing for inkos-multi-agent-novel-writing matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Fatima Ghosh· Sep 25, 2024
Registry listing for inkos-multi-agent-novel-writing matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakshi Patil· Sep 17, 2024
inkos-multi-agent-novel-writing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Aditi Sharma· Sep 9, 2024
Useful defaults in inkos-multi-agent-novel-writing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Aditi Kapoor· Aug 28, 2024
Registry listing for inkos-multi-agent-novel-writing matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Fatima Martinez· Aug 16, 2024
Useful defaults in inkos-multi-agent-novel-writing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Chaitanya Patil· Aug 8, 2024
inkos-multi-agent-novel-writing has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 31