Editaplot
liushunqi8-hash/editaplot2026
Analyze local scientific CSV, TXT, XLS, or XLSX data; recommend publication-informed charts and Chinese scientific palettes; freeze a reproducible plan; and automate editable figures through a…
A skill your agent uses when preparing, certifying, publishing, recovering, monitoring, or verifying an AutoEmailSender release; releasing repository-delivered Skills such as crawl-mentors-to-xlsx…
Install Auto Email Sender Release
$ npx skills add JunieXD/AutoEmailSender --skill auto-email-sender-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JunieXD/AutoEmailSender auto-email-sender-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JunieXD/AutoEmailSender.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/auto-email-sender-release .claude/skills/auto-email-sender-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "auto-email-sender-release" agent skill from https://github.com/JunieXD/AutoEmailSender/tree/master/.codex/skills/auto-email-sender-release into .claude/skills/auto-email-sender-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-email-sender-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JunieXD/AutoEmailSender/tree/master/.codex/skills/auto-email-sender-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JunieXD/AutoEmailSender --skill auto-email-sender-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JunieXD/AutoEmailSender auto-email-sender-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JunieXD/AutoEmailSender.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/auto-email-sender-release .agents/skills/auto-email-sender-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "auto-email-sender-release" agent skill from https://github.com/JunieXD/AutoEmailSender/tree/master/.codex/skills/auto-email-sender-release into .agents/skills/auto-email-sender-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-email-sender-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JunieXD/AutoEmailSender --skill auto-email-sender-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JunieXD/AutoEmailSender auto-email-sender-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JunieXD/AutoEmailSender.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/auto-email-sender-release .cursor/skills/auto-email-sender-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "auto-email-sender-release" agent skill from https://github.com/JunieXD/AutoEmailSender/tree/master/.codex/skills/auto-email-sender-release into .cursor/skills/auto-email-sender-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-email-sender-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JunieXD/AutoEmailSender.git --path .codex/skills/auto-email-sender-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JunieXD/AutoEmailSender --skill auto-email-sender-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JunieXD/AutoEmailSender auto-email-sender-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JunieXD/AutoEmailSender.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/auto-email-sender-release .gemini/skills/auto-email-sender-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "auto-email-sender-release" agent skill from https://github.com/JunieXD/AutoEmailSender/tree/master/.codex/skills/auto-email-sender-release into .gemini/skills/auto-email-sender-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-email-sender-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JunieXD/AutoEmailSender auto-email-sender-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JunieXD/AutoEmailSender --skill auto-email-sender-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JunieXD/AutoEmailSender.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/auto-email-sender-release .github/skills/auto-email-sender-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "auto-email-sender-release" agent skill from https://github.com/JunieXD/AutoEmailSender/tree/master/.codex/skills/auto-email-sender-release into .github/skills/auto-email-sender-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-email-sender-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JunieXD/AutoEmailSender --skill auto-email-sender-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JunieXD/AutoEmailSender auto-email-sender-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JunieXD/AutoEmailSender.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/auto-email-sender-release .opencode/skills/auto-email-sender-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "auto-email-sender-release" agent skill from https://github.com/JunieXD/AutoEmailSender/tree/master/.codex/skills/auto-email-sender-release into .opencode/skills/auto-email-sender-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-email-sender-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
auto-email-sender-release- GitHub stars
- 150
- Token cost
- ~1.2k tokens
- SKILL.md length
- 538 words
- Files
- 3 (incl. references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
A skill your agent uses when preparing, certifying, publishing, recovering, monitoring, or verifying an AutoEmailSender release; releasing repository-delivered Skills such as crawl-mentors-to-xlsx…
- Verifying an AutoEmailSender release
- SKILL.md covers Prepare, Certify and promote, Verify and Sparkle and recovery
- Calls node, uv and npm
- Releasing repository-delivered Skills such as crawl-mentors-to-xlsx
What it does
Auto Email Sender Release is an agent skill from JunieXD/AutoEmailSender. Use when preparing, certifying, publishing, recovering, monitoring, or verifying an AutoEmailSender release; releasing repository-delivered Skills such as crawl-mentors-to-xlsx; writing docs/releases/vX.md release notes; or running the cross-platform desktop, Windows VM, and macOS Sparkle release workflow.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/release-notes.md`).
It sits in Development, covering Changelog and release notes and Excel spreadsheets. It works with Microsoft Excel and macOS. The repository describes itself as: AutoEmailSender 是一个专为套磁场景设计的智能邮件助手. The licence is GPL-3.0.
When your agent uses it
- Verifying an AutoEmailSender release
- Releasing repository-delivered Skills such as crawl-mentors-to-xlsx
- Writing docs/releases/vX.md release notes
- Running the cross-platform desktop
Example prompts
- “/auto-email-sender-release”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit fad79d2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
nodeuvnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Auto Email Sender Release loads about 1.2k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 538 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from JunieXD/AutoEmailSender at commit fad79d2, republished under its GPL-3.0 licence (© JunieXD). 538 words, ~1,203 tokens.
Download SKILL.mdSave it as
.claude/skills/auto-email-sender-release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- auto-email-sender-release
- description
- Use when preparing, certifying, publishing, recovering, monitoring, or verifying an AutoEmailSender release; releasing repository-delivered Skills such as crawl-mentors-to-xlsx; writing docs/releases/vX.md release notes; or running the cross-platform desktop, Windows VM, and macOS Sparkle release workflow.
Auto Email Sender Release
Release through Prepare → Certify → Promote → Verify. Build once, then publish the certified artifacts. A request such as 发布 2.6.4 authorizes this workflow; preparation or verification alone authorizes that stage. Reconfirm changes to the version, repository or recovery scope, not already authorized publication.
Prepare
Work from master and a clean, committed candidate. Fetch origin and tags, then run:
node scripts/release/check-release-version.mjs --version <version> --repo-root .
./scripts/prepare-release.sh <version>Inspect changes since the prior release and write docs/releases/v<version>.md using release-notes.md. The app and repository Skill ZIP share a version; the Skill is a separate Release asset, not an installer component.
Certify and promote
./scripts/release.sh <version>This commits/pushes the candidate and dispatches certification without publishing. Keep the run ID and verify its SHA. Candidate certification requires preflight, CLI gate and both platform builds. On the project Mac, run formal Windows QA for the frozen candidate according to docs/operations/windows-parallels-release-qa.md; --quick is for daily checks, not release evidence.
Use the entrypoint's source checks once. It leaves frozen CLI/backend builds and their self-checks to the platform jobs that produce the release artifacts. When a full repository test run is needed, generate evidence on that first run with uv run --project backend --no-sync python scripts/quality/run_all_tests.py --write-evidence .git/release-quality-evidence.json, then pass --quality-evidence .git/release-quality-evidence.json to the entrypoint. Do not repeat a full run solely to recreate evidence already available; reuse requires the same clean SHA, toolchain and valid age. Never fabricate evidence.
For changes to release tooling or this Skill, run the affected script/packaging tests. Candidate builds, formal VM QA and publication belong to an actual release request.
When the candidate and required QA pass, publish the same artifacts:
./scripts/release.sh <version> --promote-run <candidate-run-id>Promotion verifies the candidate manifest, version, SHA, announcement and artifact hashes. It does not rebuild. Follow-up changes use node scripts/release/release-impact.mjs --base <last-certified-sha> --head HEAD to select checks; add --candidate for final certification. Never mix candidates.
Verify
./scripts/verify-release.sh <version> --candidate-run <candidate-run-id> --promotion-run <promotion-run-id>The verifier checks public artifacts, Sparkle signatures, Skill ZIP and relevant website deployment. Candidate runs require preflight, cli-gate, build-windows, build-macos, certify; promotion requires publish. Historical topology is derived by the verifier.
PowerShell has matching scripts/*.ps1 entrypoints with -PromoteRun, -CandidateRun, -PromotionRun, and -QualityEvidence parameters.
Show full SKILL.md (198 more words)Show less
Sparkle and recovery
Read docs/operations/sparkle-release-operations.md for macOS signing and isolated update QA. Generate deltas for the latest three releases. Local runs reuse data/release-cache/sparkle-dmgs/ by default, including the newly built DMG retained for next time; keep this cache between releases. CI restores the same rolling cache through Actions. Final appcast URLs must be fixed before signing; verify the whole feed and enclosure signatures against actual draft assets, uploading the feed last. Secret values must stay out of files, arguments and logs. Routine releases do not rotate keys or replace public assets.
Diagnose a failed check before retrying. Preserve the failure and thresholds; an environmental failure may justify a repeat with the same inputs, not repeated attempts until green. Use impact checks after fixes. Stale desktop build output can be removed with npm run clean before repeating the affected source test.
A public tag or asset is immutable. Reuse an unpublished tag only with user authorization and evidence that no Release, staged asset, appcast reference or successful publication exposed it. Remove only that exact local/remote tag, verify absence, and certify fresh artifacts. When publication is uncertain, investigate before retrying. Never bypass failed product checks or use --skip-verify without explicit acceptance.
© JunieXD, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in .codex/skills/auto-email-sender-release of JunieXD/AutoEmailSender.
- SKILL.md
- agents/openai.yaml
- references/release-notes.md
Open the folder on GitHubat commit fad79d2
Compare with similar skills
Auto Email Sender Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Auto Email Sender Release this skillJunieXD/AutoEmailSender | 150 | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| Editaplotliushunqi8-hash/editaplot2026 | 128 | — | ~5.8k | Automated safety check: Pass | Apache-2.0 | |
| Excel Automationdaymade/claude-code-skills | 1.4k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Enrich Exceltinyfish-io/tinyfish-cookbook | 2.2k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Compdf Conversion CLILeoYeAI/openclaw-master-skills | 2.2k | — | ~5.9k | Automated safety check: Pass | Proprietary | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Excel Automation
daymade/claude-code-skills
Create, parse, and control Excel files on macOS. An agent skill from daymade/claude-code-skills.
Enrich Excel
tinyfish-io/tinyfish-cookbook
Enrich a live Excel spreadsheet by researching missing data with TinyFish and writing results directly into the running Excel app via AppleScript.
Compdf Conversion CLI
LeoYeAI/openclaw-master-skills
MUST use for ANY PDF or image format conversion task — converting PDF and images (JPG/JPEG/PNG/BMP/TIFF/TIF/WEBP/JPEG2000) to 10 formats (Word, Excel, PPT, HTML, Image, TXT, JSON, Markdown, RTF…
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Release
eugene1g/agent-safehouse
Run the local Agent Safehouse release flow: inspect commits since the last published release, propose the next SemVer version and changelog, present a dry-run for confirmation, then update…
More from JunieXD/AutoEmailSender
Submit Mentors To Community
JunieXD/AutoEmailSender
校验、准备并通过外部 Git/gh 创建社区导师投稿 draft PR，支持查重与恢复。Use when a maintainer asks to submit, contribute, or batch-submit verified mentor/professor XLSX data to the community mentor library.
Crawl Mentors To XLSX
JunieXD/AutoEmailSender
从学校、学院、系所或实验室官网抓取公开导师/教师信息，核对个人主页与证据来源，并生成经过自动校验、可直接导入 Auto Email Sender 的 XLSX。Use when a user provides faculty, professor, mentor, supervisor, university, department, or lab directory URLs and…
Update Crawl Benchmark
JunieXD/AutoEmailSender
Safely merge one or more computers' local Auto Email Sender crawl databases into the public website benchmark JSON, normalize confirmed school aliases, verify privacy and data invariants, and run…
Auto Email Sender
JunieXD/AutoEmailSender
Operate Auto Email Sender through its local CLI for mentor and correspondence queries, drafts, campaigns, crawling, diagnosis, and confirmed email delivery.
Related
Works with
Categories
Questions about Auto Email Sender Release
What does Auto Email Sender Release do?
A skill your agent uses when preparing, certifying, publishing, recovering, monitoring, or verifying an AutoEmailSender release; releasing repository-delivered Skills such as crawl-mentors-to-xlsx…. Auto Email Sender Release is an agent skill from JunieXD/AutoEmailSender.md release notes; or running the cross-platform desktop, Windows VM, and macOS Sparkle release workflow.
When should I use Auto Email Sender Release?
Auto Email Sender Release fits situations like: verifying an AutoEmailSender release; releasing repository-delivered Skills such as crawl-mentors-to-xlsx; writing docs/releases/vX.md release notes; running the cross-platform desktop.
How do I install Auto Email Sender Release in Claude Code?
Run `npx skills add JunieXD/AutoEmailSender --skill auto-email-sender-release -a claude-code`. Or copy the skill folder (.codex/skills/auto-email-sender-release in JunieXD/AutoEmailSender) into .claude/skills/auto-email-sender-release in your project. Claude Code loads it when a task matches its description.
How do I install Auto Email Sender Release in Codex?
Run `npx skills add JunieXD/AutoEmailSender --skill auto-email-sender-release -a codex`. Or copy the skill folder (.codex/skills/auto-email-sender-release in JunieXD/AutoEmailSender) into .agents/skills/auto-email-sender-release in your project. Codex loads it when a task matches its description.
Can I use Auto Email Sender Release in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JunieXD/AutoEmailSender --skill auto-email-sender-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/auto-email-sender-release, .gemini/skills/auto-email-sender-release, .github/skills/auto-email-sender-release and .opencode/skills/auto-email-sender-release in your project.
What does Auto Email Sender Release need to run?
Going by SKILL.md and its folder, Auto Email Sender Release needs the command-line tools its instructions call (node, uv and npm). Our summary lists: Python 3.
Does Auto Email Sender Release access the network?
SKILL.md contains no URLs. Its commands use uv and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Auto Email Sender Release safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Auto Email Sender Release use?
Auto Email Sender Release is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Auto Email Sender Release use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 677 tokens, read only when the agent opens those files.
What are the alternatives to Auto Email Sender Release?
Skills that share tags, products or a category with Auto Email Sender Release: Editaplot (liushunqi8-hash/editaplot2026, 128 stars), Excel Automation (daymade/claude-code-skills, 1.4k stars), Enrich Excel (tinyfish-io/tinyfish-cookbook, 2.2k stars) and Compdf Conversion CLI (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Auto Email Sender Release?
JunieXD (a GitHub user) maintains it in JunieXD/AutoEmailSender, which has 150 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.
Source: JunieXD/AutoEmailSender on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.