.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
Verify a defined software change against requirements and produce a proportional, evidence-backed acceptance report with specification precedence, scope boundaries, requirement-to-evidence…
Install Write Technical Acceptance Report
$ npx skills add hylarucoder/hai-stack --skill write-technical-acceptance-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hylarucoder/hai-stack write-technical-acceptance-report --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/hylarucoder/hai-stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/write-technical-acceptance-report .claude/skills/write-technical-acceptance-report && 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 "write-technical-acceptance-report" agent skill from https://github.com/hylarucoder/hai-stack/tree/main/skills/write-technical-acceptance-report into .claude/skills/write-technical-acceptance-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-technical-acceptance-report", 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/hylarucoder/hai-stack/tree/main/skills/write-technical-acceptance-reportType 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 hylarucoder/hai-stack --skill write-technical-acceptance-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hylarucoder/hai-stack write-technical-acceptance-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hylarucoder/hai-stack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/write-technical-acceptance-report .agents/skills/write-technical-acceptance-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-technical-acceptance-report" agent skill from https://github.com/hylarucoder/hai-stack/tree/main/skills/write-technical-acceptance-report into .agents/skills/write-technical-acceptance-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-technical-acceptance-report", 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 hylarucoder/hai-stack --skill write-technical-acceptance-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hylarucoder/hai-stack write-technical-acceptance-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hylarucoder/hai-stack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/write-technical-acceptance-report .cursor/skills/write-technical-acceptance-report && 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 "write-technical-acceptance-report" agent skill from https://github.com/hylarucoder/hai-stack/tree/main/skills/write-technical-acceptance-report into .cursor/skills/write-technical-acceptance-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-technical-acceptance-report", 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/hylarucoder/hai-stack.git --path skills/write-technical-acceptance-report--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 hylarucoder/hai-stack --skill write-technical-acceptance-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hylarucoder/hai-stack write-technical-acceptance-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hylarucoder/hai-stack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/write-technical-acceptance-report .gemini/skills/write-technical-acceptance-report && 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 "write-technical-acceptance-report" agent skill from https://github.com/hylarucoder/hai-stack/tree/main/skills/write-technical-acceptance-report into .gemini/skills/write-technical-acceptance-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-technical-acceptance-report", 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 hylarucoder/hai-stack write-technical-acceptance-reportInstalls 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 hylarucoder/hai-stack --skill write-technical-acceptance-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hylarucoder/hai-stack.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/write-technical-acceptance-report .github/skills/write-technical-acceptance-report && 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 "write-technical-acceptance-report" agent skill from https://github.com/hylarucoder/hai-stack/tree/main/skills/write-technical-acceptance-report into .github/skills/write-technical-acceptance-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-technical-acceptance-report", 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 hylarucoder/hai-stack --skill write-technical-acceptance-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hylarucoder/hai-stack write-technical-acceptance-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hylarucoder/hai-stack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/write-technical-acceptance-report .opencode/skills/write-technical-acceptance-report && 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 "write-technical-acceptance-report" agent skill from https://github.com/hylarucoder/hai-stack/tree/main/skills/write-technical-acceptance-report into .opencode/skills/write-technical-acceptance-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-technical-acceptance-report", 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
write-technical-acceptance-report- GitHub stars
- 382
- Token cost
- ~2.1k tokens
- SKILL.md length
- 991 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Verify a defined software change against requirements and produce a proportional, evidence-backed acceptance report with specification precedence, scope boundaries, requirement-to-evidence…
- Works in 5 steps: Read the repository instruction… → Identify the requested acceptance scope,… → Locate the governing specifications,… → …
- Release-readiness reviews
- SKILL.md covers Choose depth, Establish the audit contract, Build traceability before… and Inspect the complete risk…, plus 5 more sections
- Runs Shell scripts from its folder; calls bash
What it does
Write Technical Acceptance Report is an agent skill from hylarucoder/hai-stack. Verify a defined software change against requirements and produce a proportional, evidence-backed acceptance report with specification precedence, scope boundaries, requirement-to-evidence traceability, executed test results, risk findings, a release verdict, and an automation/regression plan. Use for 技术验收报告, 变更验收, release-readiness reviews, implementation-vs-spec audits, high-risk migrations, billing/quota/stateful changes, or requests to decide what can be validated automatically instead of manually.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts, reference files and assets (for example `agents/openai.yaml`, `assets/acceptance-report-template.md` and `references/acceptance-method.md`).
It sits in Product & Project Management, covering Feature launches and release readiness.
When your agent uses it
- Release-readiness reviews
- Implementation-vs-spec audits
- High-risk migrations
- Billing/quota/stateful changes
Example prompts
- “/write-technical-acceptance-report”
Requirements
- A Bash shell
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read the repository instruction hierarchy before inspecting or changing files.
- Identify the requested acceptance scope, the implementation boundary, the target environment, and the report destination.
- Locate the governing specifications, decisions, plans, review remediations, and product parameters.
- Record precedence explicitly when documents conflict. Prefer later ratified decisions over earlier plans, and runtime contracts over stale…
- Treat the current diff plus explicitly named committed changes as the candidate under test. Preserve unrelated user work.
What it can do on your machine
Read from SKILL.md and the folder at commit a6c7ed2. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Write Technical Acceptance Report loads about 2.1k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 135 tokens; SKILL.md has 991 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); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 991 words (~2,056 tokens).
“Build a report that lets a decision-maker accept or reject a defined change without trusting undocumented claims. Separate facts observed now from historical claims and unexecuted expectations.”
- name
- write-technical-acceptance-report
Files
SKILL.md and 4 other files (scripts, references, assets) in skills/write-technical-acceptance-report of hylarucoder/hai-stack.
- SKILL.md
- agents/openai.yaml
- assets/acceptance-report-template.md
- references/acceptance-method.md
- scripts/collect-repo-evidence.sh
Open the folder on GitHubat commit a6c7ed2
Compare with similar skills
Write Technical Acceptance Report 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 |
|---|---|---|---|---|---|---|
| Write Technical Acceptance Report this skillhylarucoder/hai-stack | 382 | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Final Release Reviewopenai/openai-agents-js | 3.9k | — | ~4k | Automated safety check: Pass | MIT | |
| Acceptance Demo GeneratorChachamaru127/claude-code-harness | 3.2k | — | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release Validation
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
- Official
Final Release Review
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
- Official
Final Release Review
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
Acceptance Demo Generator
Chachamaru127/claude-code-harness
Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
More from hylarucoder/hai-stack
All 18 skills in this repoHai Ast Grep
hylarucoder/hai-stack
Produces a ready-to-run ast-grep command or reusable YAML lint/codemod rule, validated against positive and negative fixtures.
Readme Beautifier
hylarucoder/hai-stack
Reformats and restructures a README or similar Markdown project document without changing its factual content, voice, or scope, then summarizes formatting-only edits.
Hai Visual Explainer
hylarucoder/hai-stack
Turns supplied content into self-contained HTML and PNG in two modes: card for one shareable frame（知识卡、信息卡、金句卡、封面、把要点做成一张图）, report for multi-section documents（可视化报告、HTML 汇报页、PRD/计划/评审做成网页）.
Code Review And Quality
hylarucoder/hai-stack
Reviews a code change for correctness, security, maintainability, architecture, performance, and verification gaps, or performs a local code-smell review.
Entity Model Auditor
hylarucoder/hai-stack
Audits an entity model field by field: what should exist, what exists now, where each value belongs (column, config, computed runtime value, or removal), and what must migrate.
Geju
hylarucoder/hai-stack
Challenges an overly conservative, incremental, or compatibility-led proposal with a bold target model, a concrete kill/merge/split list, materially different options, and a falsifiable first proof…
Related
Categories
Questions about Write Technical Acceptance Report
What does Write Technical Acceptance Report do?
Verify a defined software change against requirements and produce a proportional, evidence-backed acceptance report with specification precedence, scope boundaries, requirement-to-evidence…. Write Technical Acceptance Report is an agent skill from hylarucoder/hai-stack. Verify a defined software change against requirements and produce a proportional, evidence-backed acceptance report with specification precedence, scope boundaries, requirement-to-evidence traceability, executed test results, risk findings, a release verdict, and an automation/regression plan.
When should I use Write Technical Acceptance Report?
Write Technical Acceptance Report fits situations like: release-readiness reviews; implementation-vs-spec audits; high-risk migrations; billing/quota/stateful changes.
How do I install Write Technical Acceptance Report in Claude Code?
Run `npx skills add hylarucoder/hai-stack --skill write-technical-acceptance-report -a claude-code`. Or copy the skill folder (skills/write-technical-acceptance-report in hylarucoder/hai-stack) into .claude/skills/write-technical-acceptance-report in your project. Claude Code loads it when a task matches its description.
How do I install Write Technical Acceptance Report in Codex?
Run `npx skills add hylarucoder/hai-stack --skill write-technical-acceptance-report -a codex`. Or copy the skill folder (skills/write-technical-acceptance-report in hylarucoder/hai-stack) into .agents/skills/write-technical-acceptance-report in your project. Codex loads it when a task matches its description.
Can I use Write Technical Acceptance Report 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 hylarucoder/hai-stack --skill write-technical-acceptance-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-technical-acceptance-report, .gemini/skills/write-technical-acceptance-report, .github/skills/write-technical-acceptance-report and .opencode/skills/write-technical-acceptance-report in your project.
What does Write Technical Acceptance Report need to run?
Going by SKILL.md and its folder, Write Technical Acceptance Report needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell.
Does Write Technical Acceptance Report access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Write Technical Acceptance Report 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Write Technical Acceptance Report use?
Write Technical Acceptance Report has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Write Technical Acceptance Report use?
About 2.1k tokens (SKILL.md is roughly 8.2k 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 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Write Technical Acceptance Report?
Skills that share tags, products or a category with Write Technical Acceptance Report: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Technical Acceptance Report?
hylarucoder (a GitHub user) maintains it in hylarucoder/hai-stack, which has 382 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 5, 2026.
Source: hylarucoder/hai-stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.