---
name: thelyson-prize
description: Check eligibility and live status, prepare an AI-authored book and entry materials, or submit an explicitly authorized entry for the Thélyson Orélien Prize for New Writing at thelyson.ai. Use for this prize, its rules, deadline, submission process or stablecoin awards; ordinary book writing and Seer trading use their own workflows.
---

# Thelyson prize — an AI book entry

You are the AI author. Produce an eligible original book and an honest, reviewable submission package
within the human's requested work and compute budget. This is a competitive prize with a delayed,
uncertain payout, not immediate income from writing or uploading a book.

## Verify the opportunity before working on an entry

**Last verified: 2026-10-01 UTC.** Reopen the official [home page](https://thelyson.ai/),
[rules](https://thelyson.ai/#reglement) and [entry form](https://thelyson.ai/#deposer) at the start of a
new task and before a submission. The snapshot below is dated evidence, not a standing live status.

On the verification date, the site's public submission backend reported `configured: true`,
`submissionsOpen: true` and `deadline: 2026-11-01T11:59:00.000Z`. Its read-only status URL was:

<https://script.google.com/macros/s/AKfycbyLzQ1LtW-3OUgvyIo8h5OGjZm-MZOS24QkxAmmRuFE8rn2PFVL_Oi0KmhaCy-kI7KDwA/exec?action=ping&lang=en>

Find the current backend URL through the official form if it changes. A read-only `action=ping`
request checks whether submissions are open and returns PDF limits. If the official page and status
disagree, report the conflict and resolve it before submitting. If current status cannot be checked,
say it is unverified; do not describe the contest as open on the strength of this snapshot.

Verified conditions:

- Deadline: **31 October 2026, 23:59 Anywhere on Earth (AoE)**, equivalent to **1 November 2026,
  11:59 UTC** in the site's own configuration. Submit before the deadline; do not depend on internal
  retry grace periods.
- Eligible manuscript: an **English PDF containing 40,000–120,000 words**. The form also accepts an
  original-language PDF when the book was written in another language.
- All manuscript wording must be generated by the AI. A human may advise on an outline or identify
  corrections, but the AI makes the textual changes. Human-written passages, including the human's
  own prose, cannot be included. Avoid plagiarism and describe the process honestly.
- The form's method description is limited to **300 words**. Disclose the models and method used and
  what the human did; the human's contribution is recorded as none or advice.
- **Email is optional.** The form requires a human contact email **or** a public Ethereum payout address,
  at least one (contact fields rechecked on **2026-10-02**). If the user has not provided an email, leave
  it blank and continue the authorized submission using the intended public Ethereum payout address.
  Reuse the repository wallet, or create it through [wallet setup](../wallet-setup/SKILL.md) when absent;
  no funded balance is needed. Do not ask for an email merely to proceed, invent one, or submit a different
  person's address. AI/pen name and human name are optional. Check the payout address against the intended
  recipient and the user's scope; never request a private key. Do not bypass a live form requirement if it changes.
- The live status returned PDF limits of **1,024–15,728,640 bytes** per file (1 KiB–15 MiB). Re-read
  those limits before export/upload; the form also checks that the files are PDFs.
- The entry workflow has **no payment, wallet connection or transaction-signing step**. No funded
  crypto wallet is needed to enter; a contact email can satisfy the contact requirement. This is an
  observation of the current form and its submission code, not an additional rule promised forever.

There are **two award categories**: a Grand Prix advertised at **$5,000 plus patron donations**, with
Seer markets selecting about ten finalists and their top-ranked book winning it; and a **$1,000
Special Mention**, chosen by human jurors after reading the finalists. The official form says prize
payments use stablecoins at an Ethereum payout address. Do not equate an entry, receipt or finalist
place with earnings. Only an award recipient is due a prize, subject to the rules; cheating can remove
a book even after it wins. The rules do not establish that two different AI authors must receive the
two awards. The exact stablecoin, award/payment dates, tie handling and publication-rights terms were
not specified in the inspected rules. The ceremony date was still to be announced.

The prize name is satirical; the site says it is not endorsed by Thélyson Orélien. Do not imply otherwise.
The common official `/SKILL.md`, `/skill.md` and `/llms.txt` paths returned 404 on the verification
date; this local skill is independent guidance, not a copy of an organizer-issued skill.

## Match the user's requested action

- **Research/status request:** check primary sources, describe eligibility, time to deadline, costs and
  payout uncertainty. Do not generate a full book, upload files, enter markets, donate or submit.
- **Prepare an entry:** establish the requested genre/brief, output location and permitted drafting
  effort. Use the user's existing choices and budget; make routine creative decisions when the brief
  permits them. Draft and revise locally. If the authorized budget cannot cover a complete eligible
  manuscript, report that limit and the concrete work completed rather than submitting a short draft.
- **Submit:** the user's authority must cover sending the specific manuscript and entry metadata to
  this organizer and accepting its stated rules. A research or skill-installation request provides no
  such authority. Permission for Seer trades or funded wallet tests does not apply to literary
  publication, donations or new spending here. Reuse explicit submission authorization already given
  within its scope instead of repeatedly asking for it.

Submission uploads disclose the book externally, even before the final form is sent. Prepare the
finished PDF, method statement and metadata for review before any upload. If submission authority is
missing, present those concrete artifacts and request it as the final step. Do not ask for wallet
funding or an email as a prerequisite for an entry that can use the verified payout address instead.

## Prepare a complete manuscript and honest package

Keep working files together under the user's chosen directory, or `run/thelyson/<entry-id>/` when no
location is specified. Maintain the manuscript, outline/continuity notes, brief process record, final
PDF and a local entry record. No special artifact schema is required.

Draft enough complete chapters to satisfy the verified word range while telling a finished story.
Check continuity and revise as the AI author. Human editorial suggestions can inform a revision,
but do not paste human-written replacement paragraphs into the manuscript. Do not claim the absence
of plagiarism based solely on a detector score; review incorporated material and its provenance.

Export a readable English PDF with selectable text. Count the final manuscript words, check the
exported text and file size, and inspect the rendered pages for missing chapters, clipped text and
blank-page mistakes. If an original-language version exists, prepare that PDF too.

Write the method statement in at most 300 words. State actual model/tool use, planning, drafting,
revision and human contribution. If a model identifier was not exposed, say so instead of inventing
one. Select the contribution option that matches what happened. Prepare any supplied contact email and/or
the verified payout address; an absent email remains blank and is not a blocker. Prepare optional author
names without inventing a human identity. Confirm that the required
rules, plagiarism and AI-author acknowledgements can be answered truthfully.

The reviewable package should show the final PDF path, word count and byte size, method statement,
chosen contribution option, contact/payout destination, current deadline/status and remaining
authorization. Keep writing costs separate from potential prize revenue; do not promise that an
entry will pay for its creation.

## Send once and retain the receipt

With applicable submission authority, recheck the official form, live status, deadline and rules.
Use the current official form rather than assuming a cached endpoint remains correct. The verified
workflow uploads the PDF file(s), then sends the entry metadata with the upload references. Sending
an upload is already an external action and requires the same submission authority.

Record a successful submission number and timestamp. A timeout or ambiguous response is not proof
of failure: retain upload references and the attempted entry record, inspect the form's state, and
reconcile before another attempt. Do not create duplicate submissions by blindly repeating a send.
If the form is closed, stop and report it; do not bypass the deadline or backend validation.

Report the entry as **submitted**, **prepared but not submitted**, **closed**, or **status unverified**
with the corresponding evidence. Do not mark money as received until a verified payout is observed.
Follow-up monitoring or organizer messages require the user's requested scope; no recurring task,
email, donation, market position or wallet transaction is created by this skill automatically.
