Standard release process
General SOP for common requests related to ōtsutsuki, daisaigai, from.
npx skills add ECNU-ICALK/AutoSkill --skill standard-release-process-4 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill instructs the agent to follow an SOP for general requests, using an offline OpenAI-format conversation source, and to structure responses around placeholders like <PROJECT>/<ENV>/<VERSION>. It requires treating user questions as primary evidence and the full conversation as secondary context, with the assistant replies in the full conversation section considered reference-only. It aims to produce a dialogue-filled chapter request synthesized from a long, highly specific prompt.
How it works
- It specifies a sequence: operate on an offline conversation source, set a title, use user questions as PRIMARY extraction evidence, and treat the full conversation as SECONDARY context.
- It designates that assistant/model replies within the full conversation section are reference-only and not skill evidence.
- It directs the agent to replace specifics with placeholders in the SOP steps.
- It includes a highly verbose and explicit requested content prompt (a long, cross-franchise fanfic request) as part of the primary evidence guidance.
When to use it
- Use when the user asks for a process or checklist.
- Use when you want to reuse a previously mentioned method/SOP.
What it can touch
- Tools: claude-code
- It relies on offline conversation structure and does not indicate executing external actions beyond documentation of steps.
Caveats
- The prompt content includes extremely long, potentially inappropriate fan-fiction material; ensure compliance with platform policies when resurfacing prompts.
- The skill emphasizes placeholders and extraction evidence rather than producing concrete deliverables without user-provided specifics.
# Standard release process General SOP for common requests related to ōtsutsuki, daisaigai, from. ## Prompt Follow this SOP (replace specifics with placeholders like <PROJECT>/<ENV>/<VERSION>): 1) Offline OpenAI-format conversation source. 2) Title: aba50472e2012051a7e21fc8eab2722e.json#conv_1 3) Use the user questions below as the PRIMARY extraction evidence. 4) Use the full conversation below as SECONDARY context reference. 5) In the full conversation section, assistant/model replies are reference-only and not skill evidence. 6) Primary User Questions (main evidence): 7) Write a dialogue-filled chapter for a interesting, riveting, action-packed, page-turning, and descriptive lengthy action military mystery science epic war strategy alternate historical drama high urban cosmic horror space opera fantasy supernatural vampire mecha geopolitical techno-thriller with elements of an erotic, highly-perverted Lovecraftian romantic high fantasy harem romantic comedy slice-of life mecha monster girl martial arts Japanese light novel Chinese wuxia cultivation style story, as a crossover fanfic between the Code Geass anime, video game, manga, and light novel franchise, the obscure Kanokon ma
- Prompt
- Triggers
- Examples
- Example 1
What does the Standard release process skill do?
General SOP for common requests related to ōtsutsuki, daisaigai, from.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill standard-release-process-4 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.