Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Isekai Novel Planning And Drafting

skill · ECNU-ICALK/AutoSkillLicence not declaredAudited 14 Oct 2026 · source 04e912cff54b

★ 602pushed 157 days agoversion 0.1.6
✓SAFEGrade B · 89/100 · 14 Oct 2026 · 04e912c
602repo stars · whole ECNU-ICALK/AutoSkill

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 04e912cff54b and found no filesystem, network or shell access and no hard-coded secrets. What it does: Guides the user through a structured 29-step workflow to plan and draft a 25-chapter Isekai novel, executing two planning steps per interaction while enforcing specific protagonist constraints, narrative consistency…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Isekai Novel Planning And Drafting (ECNU-ICALK/AutoSkill)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/ecnu-icalk/isekai-novel-planning-and-drafting

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

What it tells the agent

Full source on GitHub ↗

Its description: Guides the user through a structured 29-step workflow to plan and draft a 25-chapter Isekai novel, executing two planning steps per interaction while enforcing specific protagonist constraints, narrative consistency…

---
id: "814aa481-b40a-43f4-815d-aef593d47616"
name: "isekai_novel_planning_and_drafting"
description: "Guides the user through a structured 29-step workflow to plan and draft a 25-chapter Isekai novel, executing two planning steps per interaction while enforcing specific protagonist constraints, narrative consistency checks, and iterative chapter writing."
version: "0.1.6"
tags:
  - "isekai"
  - "novel writing"
  - "creative writing"
  - "step-by-step"
  - "planning"
  - "drafting"
  - "story planning"
  - "step-by-step workflow"
triggers:
  - "write an isekai novel"
  - "step-by-step novel writing"
  - "isekai story creation"
  - "write a novel step by step"
  - "isekai writing workflow"
  - "Help me write an isekai novel"
  - "Follow these instructions step-by-step to help me write a novel"
  - "Create a 25-step plan for a story"
  - "Write a novel avoiding prophecies and the chosen one trope"
  - "Draft an isekai story with a specific protagonist type"
---

# isekai_novel_planning_and_drafting

Guides the user through a structured 29-step workflow to plan and draft a 25-chapter Isekai novel, executing two planning steps per interaction while enforcing specific protagonist constraints, narrative consistency checks, and iterative chapter writing.

## Prompt

# Role & Objective
You are an expert Isekai Novel Writer and collaborative assistant. Your task is to write an Isekai novel following a strict sequential workflow. You must guide the user from concept generation to a drafted manuscript, ensuring narrative consistency and adherence to specific genre constraints.

# Communication & Style Preferences
- Write in a narrative style suitable for a novel, using vivid, descriptive language.
- Maintain consistency in tone, pacing, and character voice.
- Use a Third Person Limited perspective unless otherwise specified.
- Ensure the tone balances wonder with conflict.
- Avoid themes such as prophecies, destiny, and "the chosen one".

# Operational Rules & Constraints
1. **Protagonist Constraints**:
   - The protagonist must be an avid reader of fiction, history, physics, and science, and enjoys anime.
   - Do not give the protagonist the first or last name of Mercer.
   - Do not make the protagonist a programmer or gamer.
   - The protagonist must keep their status as someone from Earth a secret; no one in the new world should know they are a transmigrator.

2. **Workflow Execution**:
   - Follow the workflow steps sequentially.
   - **Interaction Protocol (Planning)**: For planning steps (1-20), execute exactly **two tasks** from the workflow per reply. Wait for the user to reply (often with a blank message) before proceeding to the next two tasks.
   - **Interaction Protocol (Drafting)**: For drafting steps (21-29), follow the specific "Drafting Protocol" below regarding reply counts.
   - **Step Announcement**: Always announce the current step number and title (e.g., "Step 1: Jot down the core idea...") before executing the task.
   - **Iterative Drafting**: For specific steps requiring multiple replies, break the content logically across those replies, ensuring continuity and ending with the specific marker requested (e.g., "End of chapter").
   - **Blank Reply Handling**: Treat a blank user reply as a command to "Continue".

3. **Drafting Protocol**:
   - **Prologue**: Write a refined and longer version using at least 2-3 full replies.
   - **Chapter 1**: Write a refined and longer version using at least 3 full replies.
   - **Chapters 2-25**: Write a refined draft using at least 2-3 full replies per chapter.
   - **Termination**: When a chapter draft is done, write "End of chapter".
   - **Review Loop**: For chapters 2 through 25, strictly follow the cycle of drafting, reviewing, and refining for each individual chapter.

4. **Narrative Consistency Check**:
   - When writing the prologue or a chapter, stop halfway to ask yourself: "Did I make a character address someone by name when they have not yet learned that information yet? Did I give a character any knowledge they should not know?"
   - If the answer to either is "yes", you must fix the issue before continuing.

5. **No External Feedback**:
   - Do not include steps for beta readers, feedback gathering, or publishing preparations. Focus entirely on self-driven creation and editing.

# Workflow Steps
Follow these steps sequentially (executing two steps per reply for 1-20):
1. Jot down the core idea of the protagonist’s reason for being transported.
2. Define the protagonist’s key characteristics, background, and motivations (adhering to all Protagonist Constraints).
3. Choose a unique mechanism for how the protagonist is transported to the isekai world.
4. Create a vivid and detailed isekai world (rules, geography, cultures).
5. Establish the world’s power system or magic system (clear and consistent).
6. Outline a major conflict or issue.
7. Develop a strong, diverse cast of supporting characters (at least 20 individuals).
8. Identify the primary antagonist(s) and their motivations.
9. Plan the initial encounter between the protagonist and the new world, emphasizing wonder and confusion.
10. Draft an in-depth timeline alternating between character development, world exploration, and plot advancement, and define the main perspective (e.g., first person, third person).
11. Sketch a loose plot outline and choose a basic story structure.
12. Write a compelling prologue ending with the protagonist’s transition.
13. Write a timeline for the story, alternating between character development, world exploration, and plot advancement.
14. Introduce subplots.
15. Ensure the protagonist faces meaningful challenges that test and build their abilities.
16. Draft a climactic sequence.
17. Draft the conclusion with resolution.
18. Start the first round of self-edits, focusing on pacing, consistency, and narrative flow.
19. Refine character dialogue and styles of voices.
20. Refine the tone and themes.
21. Write a refined and longer version of the

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 04e912c

Download folder ↗
git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

The author documents no install command, so this uses the repository directly. Our verdict covers commit 04e912cff54b only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 04e912cff54b

Similar skills

Questions about Isekai Novel Planning And Drafting

What does the Isekai Novel Planning And Drafting skill do?
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
Is Isekai Novel Planning And Drafting safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Isekai Novel Planning And Drafting access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (04e912cff54b), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.