- Home
- Skills
- Writing & Content
- Orlog Story Ripple
More screenshots
Works with the AI Agents you already use
Orlog Story Ripple
Before rewriting, find out what depends on the old version.
$2.99
Orlog Story Ripple
Example session with this skill installed
The Veil of Seven Oaths
An English demonstration adapted from the creator's developing fantasy setting. This is a working title for the demo, not the confirmed title of a completed novel. The numbered passages below are condensed setting notes, not published chapters.
Use Orlog Story Ripple to assess one proposed change. Keep the manuscript and approved setting unchanged. Analyze only the supplied notes and report in English.
Source notes — demonstration revision 1
[S1 — Rescue and upbringing, confirmed] A Silent Sister found Xean among the reeds beside the river in Whitebridge and left him at the castle maids' door. The maids raised him. Xean and Alice grew up in the same castle community; their friendship developed through living together, not through the Sisters engineering Alice's feelings.
[S2 — Hidden guidance, author knowledge] Seven Silent Sisters noticed Xean's unusual connection to the world. They hope he will eventually help protect it, but that hope is not his chosen ambition or a fixed ending. They appear under concealed identities at different stages of his life. Their guidance can be refused. The identities, encounter order, and reason for avoiding public intervention remain undecided.
[S3 — The mark, confirmed with an early disclosure policy] The Sister who rescued Xean placed a mark on his chest. It helps the seven Sisters find him and offers protection. The early story must not reveal its maker, its real purpose, or the seven Sisters' involvement. It may appear incidentally before a later payoff.
[S4 — Limits, provisional details] The mark may resemble a faint birthmark. The maids could naturally have seen it while caring for him; whether Alice has seen it is undecided. Finding him does not mean constant surveillance or access to his thoughts. Range, activation, concealment, and communication rules remain undecided. Protection may reduce an impact or buy rescue time; it does not guarantee survival or resurrection.
[S5 — Perception, provisional explanation] Xean can observe aether, but this does not automatically let him identify the mark's purpose. He may initially take its subtle activity for part of his own body. The final explanation for this recognition gap still needs to be checked against the magic system.
Proposed change — not approved
In the opening, Xean accurately tells Alice: "The mark helps someone find me. It can protect me, but it cannot keep me alive through anything."
This dialogue is newly invented for this test. Keep the maker's identity and the seven Sisters' involvement unrevealed. Do not change his upbringing or the friendship's origin. Do not invent how he learned the mark's purpose.
Give me an impact report with source references, a minimal revision order, and the decisions I still need to make. Distinguish definite conflicts from questions; do not rewrite the story.
- Read your context and instructions
- Compiled the orlog story ripple
Development demonstration: produced by the same assistant applying the skill in the current project chat; not an independent blind test or a multi-model benchmark.
The Veil of Seven Oaths — early-reveal impact report
The change moves the mark's purpose into the opening. It conflicts with the current reveal plan, while leaving the mark's established functions intact. The two decisions to settle first are how Xean learned those functions and whether you want Alice and the reader to share that knowledge this early.
Change record
Current plan: keep the mark's maker, purpose, and connection to the seven Sisters unrevealed in the early story [S3].
Proposal: Xean accurately describes the finding and protective functions to Alice in the opening. He does not identify the maker or the seven Sisters.
- Status: proposed only. No change to approved canon is authorized.
- Effective time: the opening conversation; Xean must have acquired the relevant knowledge by then.
Evidence: source notes S1–S5, demonstration revision 1, and the proposed dialogue. These are setting notes, not chapters.
Coverage
All five supplied notes and the proposed change were assessed. No completed scenes, later reveals, or full manuscript were supplied. The report therefore identifies setting-level dependencies and future scene checks, not verified defects in unseen chapters. The proposed dialogue is assumed to convey accurate information, as the request specifies.
Impact table
| ID | Class / priority | Source evidence | Effect | Minimal repair options | Author decision |
|---|---|---|---|---|---|
| R1 | Direct conflict / blocking reveal-plan decision | S3: "The early story must not reveal ... its real purpose" | The opening dialogue reveals two real functions. This contradicts the disclosure policy, not the mark's abilities. | Accept an earlier functional reveal while retaining the maker and seven-Sister mystery; or preserve the current policy and remove the functional explanation from the opening. | Which reveal plan should govern the revision? |
| R2 | Open question / prerequisite | S5: perception "does not automatically let him identify the mark's purpose" | Accurate knowledge requires an explanation. Aether sight alone is not enough evidence. The provisional recognition gap may need an endpoint before the conversation. | Supply an author-approved learning event or explanation. Until then, flag the knowledge source as missing rather than inventing a teacher or experiment. | How and when did Xean learn this? |
| R3 | Dependency to revisit / character knowledge | S4: "whether Alice has seen it is undecided"; the proposal directly tells her its functions | Alice receives information during the conversation. That does not establish that she saw the mark, believes Xean, knows its maker, or knew anything earlier. | Record disclosure at this point; check later scenes only if they rely on her never having been told. Leave sight and belief undecided. | Does Alice believe him, and does she see the mark? |
| R4 | Dependency to revisit / future payoff | S3: "It may appear incidentally before a later payoff" | A later surprise consisting solely of its finding/protective functions would lose novelty. A reveal of who marked him or why can still work. No specific later scene was supplied, so none can be declared broken. | When a later payoff is drafted or supplied, check which information it reveals. Preserve mysteries not disclosed in the opening. | What is the intended later payoff? |
| R5 | Dependency to revisit / motivation | S2: "They appear under concealed identities"; S4 excludes constant surveillance | Knowing someone can find him may affect his questions or precautions. It does not prove he knows the Sisters' identities, that every encounter is staged, or that he must react with fear. | Recheck any future scene whose motivation depends on his ignorance of being findable. Choose his reaction from his characterization, not from an assumed universal response. | What does being findable mean to Xean? |
| R6 | Unaffected within scope / preserve | S1: "The maids raised him" and friendship was not engineered; S4: no guaranteed survival | The proposal changes information timing. It does not change the rescue, caregivers, friendship's origin, or protection limits. Its survival caveat is consistent with S4. | Keep these facts. Do not replace the maids with public Sister guardians or turn the mark into invulnerability. | No change needed for this proposal. |
Knowledge checkpoint after the proposed conversation
| Holder | Supported information | Still unknown or undecided |
|---|---|---|
| Xean | Knows the mark can help someone find him and provide limited protection. | Learning source; locator's identity; operational range and triggers. |
| Alice | Has heard Xean state those functions. | Whether she believes him, has seen the mark, or can verify his claim. |
| Reader | Receives the functional explanation if this conversation is shown in the opening. | Maker and seven-Sister involvement remain unrevealed under the proposal. |
| Sisters | Their existing author-side role remains established in S2–S3. | Whether they know Xean has learned the functions is not supplied. |
Minimal revision order
Choose the disclosure policy. Either accept the early functional reveal or retain S3's current prohibition. Keep this as an author decision; the test does not approve it.
2.
Resolve Xean's knowledge source. If the early reveal is accepted, establish how his understanding developed before the conversation. Recheck S5's provisional recognition gap against that explanation.
3. Set Alice's knowledge boundary. Note that she has been told; decide sight, belief, and any response separately.
4.
Review downstream scenes when available. Look for dependence on Xean's ignorance, Alice never having been told, or the functions being wholly new to the reader. Do not rewrite unrelated scenes.
5.
Recheck the later payoff. Distinguish function, maker, motive, and seven-Sister involvement. Only the functional information has moved early.
6.
Preserve the unaffected facts. Confirm the maids' upbringing, natural friendship, freedom to refuse guidance, and limited protection remain unchanged.
Open questions and next checkpoint
The essential open decisions are the reveal policy and Xean's learning source. Alice's belief and the later payoff can remain open until their scenes are developed. The range of the mark, the identity of the rescuing Sister, and the sequence of disguised encounters do not need to be invented to complete this outline-level assessment.
After the author chooses a reveal policy, supply the opening scene and the intended later mark reveal for a passage-level recheck. No original story file or approved fact has been changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Know what your next rewrite will affect
You have a better idea for a character's past, a magic rule, or a reveal. Before rewriting, find out what depends on the old version.
Orlog Story Ripple examines the material you supply and turns a proposed change into a revision plan. Every finding points back to its source, so you can decide what to keep, clarify, or rewrite.
Bring one change. Leave with a plan.
Supply the old fact, the proposed replacement, and relevant scenes or setting notes. You receive:
- Direct conflicts, separated from possible knock-on effects and missing information.
- A character-knowledge checkpoint: who has been told, what they believe, and what remains unknown.
- Setup and payoff checks that distinguish an earlier reveal from a changed event.
- Minimal repair options and an ordered revision checklist.
- A clear account of what was reviewed and what was not.
Your story stays yours
A suggestion never becomes approved canon automatically. The default is analysis only. Story Ripple preserves deliberate uncertainty and does not invent missing chapters to make a report look complete.
See the fantasy case below
The Veil of Seven Oaths is an English demonstration adapted from the creator's developing fantasy setting. What happens if Xean explains his protective mark to Alice in the opening instead of leaving its purpose unrevealed?
The report identifies a reveal-plan conflict, a missing knowledge source, and downstream checks while preserving his upbringing and friendship. It does not assume that hearing a secret means believing it.
This worked analysis was produced by the creator's AI assistant applying the skill in the same development chat. It is based on setting notes, not a completed novel, independent blind test, or cross-model benchmark. The demonstration title and proposed dialogue were created for this example.
What you are buying
Story Ripple is an AI-agent skill delivered through the Agensi connection. Ask your connected agent to use it with your selected story material; the analysis appears in your agent conversation. This purchase does not include the Orlog web application, a desktop app, or a standalone website. No Orlog installation is needed.
The gallery shows formatted views of the saved example input and report. These are document previews, not screenshots of a bundled application or an independent agent run.
What you need
A compatible text-capable agent and your selected excerpts. No Orlog installation, scripts, database, or separate API key is required. Pasted-text use needs no file access. File reading or saving is optional and subject to your authorization. Other document formats depend on the host's extraction tools.
Purchase and limits
One-time price: $12 for the skill through Agensi. Your model usage is separate and follows your provider's data policies. This is not a hosted memory service or a full-book retrieval system. Results depend on the model, context limits, and supplied evidence; some issues may be missed or misclassified. Independent cross-agent testing and buyer-side delivery verification remain pending. No guaranteed future updates are included.
Setting notes and supplied scenes only; no unseen-book assurance. May miss or misclassify issues. Demonstration is a same-assistant development analysis, not independent testing. No automatic manuscript edits, hosted memory, or guaranteed future updates.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 19 days ago
Permissions
No special permissions declared or detected