AGENT SKILL

deloreis

Keep fiction and worldbuilding consistent with De Lore Is. Use when maintaining lore for AI-assisted novels, series bibles, campaigns, competing story ideas, retcons, or checks on generated additions to a fictional world. Record and query persistent lore through local MCP tools. Also use for explicit De Lore Is, DLI, or deloreis project requests.

License 许可
MIT
所属仓库
bg-szy/TOP-SKILLS
最近更新
2026-11-15
Stars
★ 6
Forks
0

01 前言 Front Matter

name
deloreis
license
MIT
description
Keep fiction and worldbuilding consistent with De Lore Is. Use when maintaining lore for AI-assisted novels, series bibles, campaigns, competing story ideas, retcons, or checks on generated additions to a fictional world. Record and query persistent lore through local MCP tools. Also use for explicit De Lore Is, DLI, or deloreis project requests.

02 资源文件 2

03 SKILL.md 正文

Authoring with De Lore Is

Use De Lore Is when a writing task needs an established world to check against: continuing a novel, adding lore, revising an account, or exploring another version of a story. It records structured lore and checks the rules supplied for that world. Keep the manuscript and prose references in their existing files.

For installation and a complete first check, read First session. The skill does not install the runtime. Start with a small section of the user's notes, not a whole-book migration. Ask which details are established and which are ideas. Propose rules instead of assuming, for example, that every character can have only one home.

Use the author.* tools to add lore. Read every returned finding. Repair mechanical input errors; resolve continuity findings using the user's rulings rather than change lore just to make a check pass. Do not edit .dli as an agent authoring a world. People can write .dli directly and import or check it; the store is the source of truth for an authoring session.

Register deloreis mcp --project <directory> with the client, then call its tools. If they are not available, use the first-session setup instead of simulating a stored world in the chat. The server also offers newline-delimited JSON through deloreis serve --project <directory>. Contract 2.0.0 is the served contract. --tools all advertises specialist tools beyond the default profile. Use installed help and tools/list for the exact arguments rather than guessing tool schemas.

Authoring loop

  1. author.open a scope and retain its returned workspace ID and digest. When fencing writes, pass the current digest as expected_digest; read the updated workspace_digest from the result or author.status after each change rather than reuse an earlier one.
  2. Use typed operations such as author.add_entity, author.add_fact, author.add_relation, author.add_event, and author.add_before. Declare single-valued predicates with author.declare_functional and changing predicates with author.declare_inertial where appropriate.
  3. Check the project's source/decision index before choosing a new decision ID; reuse an ID only for that same ruling. For a ruling, use author.record_decision and cite that decision with {"kind":"cited","decisions":["d-0001"],"state":"ratified"}. An unruled proposal can use {"kind":"proposed","origin":"session-name"}. Unknown citations are errors and cannot make a claim certain.
  4. Inspect author.check, author.findings, author.query, and author.why. author.diff shows staged consequences. Check the returned findings even if the call itself succeeded.
  5. author.materialize checks and commits staged changes. It refuses errors. author.discard rejects staged work. Keep returned root hashes and claim IDs when they are useful for review or later retcons.

author.record_decision, author.defeat, and standing operations can update the store directly; do not assume that every mutation is only staged. Use the user's agreed rulings and the host's review policy before these calls; do not silently turn an idea into an accepted account. The caller supplies attribution, decision state, and review policy. The server checks references and continuity, not who is authorized to rule.

Use it during a writing task

  • Continue a chapter: query the people, places, and established facts relevant to the scene. After drafting, propose the new factual claims through the tools, check them, and show the user any conflicts. Review extracted claims against the prose; a clean check covers those claims and recorded rules.
  • Brainstorm: keep alternatives proposed or in a hypothetical fork. Use author.open_question and author.add_option for a choice between accounts; author.add_hypothesis and author.suppose support hypothetical exploration. Accepting a note into the store does not by itself make it established canon. Query established claims with layer: "certain". Use layer: "possible" or "all" to inspect open accounts as well; those layers also include certain claims. A known claim can evaluate dead, but there is no dead query layer: inspect its blocked support with author.why.
  • Revise: inspect author.diff and author.why, then record the user's chosen new ruling before calling author.defeat on the earlier support. Retain the old claim ID. Use a named branch for a separate durable version; branch tools are advertised with --tools all.
  • Track change within the story: record event-anchored states and query author.as_of. A character changing allegiance is not necessarily a retcon. Declare known event ordering; leave unknown ordering open.

New workspaces see current committed lore; an already-open workspace retains its base. Open a fresh workspace when another session has changed the accepted world. The host application owns approval, access control, and concurrent-write policy. Do not describe DLI as general-purpose agent memory or infer a character's knowledge from world facts.

For CLI reads and wiki export, see Read and export.

Core tools

The default MCP profile keeps 29 common tools. It advertises dli.check, dli.name.check, and:

  • Workspace and inspection: author.open, author.status, author.check, author.findings, author.predicates, author.query, author.why, author.as_of, author.diff, and author.entity_candidates.
  • Lore: author.add_entity, author.add_fact, author.add_relation, author.add_event, author.add_before, author.add_state, author.declare_functional, and author.declare_inertial.
  • Rulings and exploration: author.record_decision, author.open_question, author.add_option, author.defeat, author.set_standing, author.add_hypothesis, and author.suppose.
  • Acceptance: author.materialize and author.discard.

author.add_option can name a fact that follows if that option is chosen, using its optional implies field. Give options distinct names and add them before materializing their question.

Use tools/list for the exact schemas. author.query returns claim IDs when available; author.why explains supporting and blocked paths. For a retcon, author.defeat takes a claim ID, a new decision, and the decision it defeats. Defeating the retcon can restore the original support. Use --tools all for named branches, specialist authoring, corpus import/export, and other tools.

The Holmes casebook is produced from a replay that exercises the server. The concept glossary explains the terms. DLI checks structured claims, not prose, and a functional conflict is detected only for a predicate declared single-valued.

Reading rendered lore

These are supported readable .dli forms. Agents author through the tools instead of editing these snippets into the project:

person wren "Wren" proposed session
functional home proposed session
home(wren, thornfield) ratified d-0001

04 同仓库更多 Skills

bg-szy
bg-szy/TOP-SKILLS

serpmaven

Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-landing-page-audit

Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-growth-context

Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-get-listed

Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-ai-readiness-audit

Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

proxy-troubleshooting

Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.

★ 6