asc-whats-new-writer
by rudrankriyamasc-whats-new-writer turns git logs, bullets, or free text into localized App Store Connect What’s New copy, using canonical metadata in `./metadata` and optional promotional text updates. It is designed for release managers, app marketers, and SEO Content teams that need a repeatable asc-whats-new-writer guide with less guesswork.
This skill scores 83/100, which means it is a solid listing candidate for Agent Skills Finder: users can reasonably expect a real, triggerable workflow for generating App Store release notes, with enough structure to reduce generic-prompt guesswork, though it still has some adoption caveats.
- Explicit trigger and input modes: git log, bullet points, or free text, with auto-detection guidance in SKILL.md.
- Strong operational guidance: preconditions, metadata location rules, locale handling, and a step-by-step workflow make execution more deterministic.
- Useful repository support: a dedicated release_notes_guidelines reference provides tone, structure, and anti-pattern guidance for better output quality.
- No install command or helper scripts are provided, so users must wire up the skill and environment themselves.
- The workflow is tightly focused on App Store What's New copy and depends on local metadata/auth setup, limiting out-of-box usefulness.
Overview of asc-whats-new-writer skill
asc-whats-new-writer is a release-notes writing skill for App Store Connect workflows. It turns git logs, rough bullets, or free text into localized “What’s New” copy, with support for canonical metadata in ./metadata and optional promotional text updates. If you need the asc-whats-new-writer skill for SEO Content teams, app marketers, or release managers who want polished release notes without starting from a blank page, this is built for that job.
What it is best for
Use asc-whats-new-writer when you already know what shipped, but need to translate technical or scattered input into user-facing language. It is most useful for teams that release often, maintain multiple locales, or want consistent App Store tone across versions.
What makes it different
The skill is not just a generic prompt for release notes. It is guided by release-note rules, locale awareness, and a workflow that expects real app metadata. That makes asc-whats-new-writer more decision-ready than a one-off prompt, especially when you need copy that reads well on the App Store and can be reused across versions.
When it is a strong fit
Choose asc-whats-new-writer if your source material is messy but your output needs to be concise, benefit-led, and publishable. It fits teams that can provide git history, bullets, or change summaries and want the skill to shape them into better storefront copy.
How to Use asc-whats-new-writer skill
Install asc-whats-new-writer
Install the asc-whats-new-writer skill in your skills directory with the repo path shown in the project docs. In practice, the install step should point to rudrankriyam/app-store-connect-cli-skills and the skills/asc-whats-new-writer folder. After install, confirm you can open SKILL.md and the reference guideline file before asking for output.
Start with the right inputs
asc-whats-new-writer works best when you supply one of three inputs: a git log range, a short bullet list, or a plain-language change summary. Strong prompts name the app, release version, locale, audience, and the exact changes to include or exclude. Weak prompts like “write release notes” force the skill to guess too much.
Suggested reading order
Read SKILL.md first, then references/release_notes_guidelines.md. That gives you the tone rules, the 170-character hook guidance, and the section structure before you write prompts. If your repo has a metadata pull process, check the latest version directory and locale files so the skill writes against the correct release data.
A practical usage pattern
A good asc-whats-new-writer usage flow is: collect changes, remove noise, map them to user benefits, then draft localized copy. Example prompt shape: “Use the latest metadata in ./metadata, summarize only user-facing changes from these commits, write an en-US What’s New draft, and keep the first sentence hook strong for the App Store.” That kind of instruction gives the skill enough structure to perform well.
asc-whats-new-writer skill FAQ
Is asc-whats-new-writer only for App Store release notes?
Yes, primarily. The asc-whats-new-writer skill is centered on App Store Connect “What’s New” copy and nearby promotional text, not general blog content or long-form product marketing. If you need website SEO pages, this is the wrong tool.
Do I need metadata before using it?
Not always, but metadata improves accuracy. If canonical files are available under ./metadata, the skill can align output to the latest version and locale. If not, it can still work from bullets or free text, but you should expect to provide more context yourself.
How is this different from a normal prompt?
A normal prompt may generate passable release notes once. asc-whats-new-writer gives you a repeatable process: what input to gather, what noise to remove, what tone to follow, and what files to inspect first. That matters when you need consistent output across releases.
Is asc-whats-new-writer beginner-friendly?
Yes, if you can describe what changed. Beginners should start with bullet points instead of raw git logs, because bullets are easier to turn into user-facing benefits. The skill still expects you to know the app, version, and intended locale.
How to Improve asc-whats-new-writer skill
Give the skill better source material
The biggest quality jump comes from cleaner inputs. Instead of “fixed bugs and improved performance,” provide concrete, user-visible changes like “reduced login failures on weak connections,” “added export to CSV,” or “improved search results for saved items.” This helps asc-whats-new-writer produce copy that sounds specific and credible.
State the constraints up front
If there are word limits, localization needs, banned phrases, or must-mention features, include them in the prompt. asc-whats-new-writer performs better when it knows whether to prioritize a punchy hook, a three-part New/Improved/Fixed structure, or a stricter App Store tone.
Review the hook first
For release notes, the first line carries the most weight. When you iterate on asc-whats-new-writer output, test the opening sentence before polishing the rest. If the hook does not clearly tell users why the update matters, ask for a more benefit-led rewrite with one primary outcome.
Improve by iterating on exclusions
A common failure mode is over-including internal changes. Tell the skill what to ignore: refactors, dependency bumps, CI updates, or copy that is not user-facing. If the first draft feels too broad, narrow the prompt with a short exclusion list and rerun asc-whats-new-writer for a tighter final version.