Standard release process
General SOP for common requests related to dai, teikoku, nihon.
npx skills add ECNU-ICALK/AutoSkill --skill standard-release-process-3 --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 offline OpenAI-format conversation source workflow to generate a historical documentary chapter in an alternate-history setting. It specifies a series of steps for extracting evidence from user questions and full conversation, and to write a plausible alternate-history narrative without references to this being alternate history.
How it works
The agent is guided to:
- Use an offline OpenAI-format conversation source.
- Set the Title to bc41612fbf347a9f5fa3256351de655d.json#conv_1.
- Treat the user questions as PRIMARY extraction evidence and the full conversation as SECONDARY context.
- Consider assistant/model replies in the full conversation as reference-only and not skill evidence.
- Write a plausible alternate-history documentary chapter with no references to alternate history or real-world timelines.
- Follow a placeholder-based SOP structure with placeholders like <PROJECT>/<ENV>/<VERSION>, replacing specifics accordingly.
- Endorse a restoration of the Dai Nippon Teikoku/Dai Nihon Teikoku government, while acknowledging Tokugawa-era elements and a Meiji-era restoration of certain offices.
When to use it
Use when the user asks for a process or checklist, or when reusing a previously mentioned method/SOP.
What it can touch
The skill declares the tool claude-code for execution.
Caveats
The content is extremely long, with heavy fictional/alternate history elements and placeholders. It relies on an offline prompt structure and includes explicit references to historical entities and hypothetical political scenarios; no license or risk section is provided in the text above. Any limitations or risks are not stated beyond the procedural notes and the emphasis on alternate-history construction.
# Standard release process General SOP for common requests related to dai, teikoku, nihon. ## Prompt Follow this SOP (replace specifics with placeholders like <PROJECT>/<ENV>/<VERSION>): 1) Offline OpenAI-format conversation source. 2) Title: bc41612fbf347a9f5fa3256351de655d.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 realistic, sensible, plausible and alternate history scenario in the form of a historical documentary book chapter set in the world of the alternate historical scenario with no references to this being an alternate history scenario or to the real world timeline at all, in which the Dai Nippon Teikoku/Dai Nihon Teikoku [the Dai Nippon Teikoku/Dai Nihon Teikoku [Great Empire of Nihon/Great Nihon-jin |Japanese (Nihon-jin)| Empire/Great Nihon/Third Nihon-jin Empire/Imperial Nihon/Nihon-jin Empire |Dai Nippon Teikoku/Dai Nihon Teikoku|], a unitary parliamentary semi-constitutional democratic federalist absolute imper
- Prompt
- Triggers
- Examples
- Example 1
What does the Standard release process skill do?
General SOP for common requests related to dai, teikoku, nihon.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill standard-release-process-3 --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.