Maintains and surfaces markdown change proposals within the repository, integrating with native review flows.
Install
mkdir -p .claude/skills/humblestudio-proposal-artifact-loop && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13577" && unzip -o skill.zip -d .claude/skills/humblestudio-proposal-artifact-loop && rm skill.zipInstalls to .claude/skills/humblestudio-proposal-artifact-loop
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when extending HumbleStudio's native review flow around markdown change proposals stored in the repository.Key capabilities
- →Save proposal artifacts into `docs/change-proposals/` with predictable filenames.
- →List matching proposals for the current selection.
- →Surface proposal linkage in adjacent review or navigation inspector summaries.
- →Show scope, coverage, evidence, updated time, and richer proposal metadata.
- →Support refresh and open/reveal actions for proposals.
How it works
This skill saves markdown change proposals to a designated repository path and makes them visible within HumbleStudio's native review interface, ensuring consistent artifact management.
Inputs & outputs
When to use humblestudio-proposal-artifact-loop
- →Document a new feature proposal
- →Surface existing change proposals
- →Verify proposal coverage
About this skill
HumbleStudio Proposal Artifact Loop
Use when extending HumbleStudio's native review flow around markdown change proposals stored in the repository.
Goals
- keep proposal capture repo-aware and stable
- let reviewers read proposal artifacts back inside the macOS app
- preserve a strict boundary between proposal authoring and future write-back
Workflow
- Start from native review context:
- component id or view id
- evidence path
- preview coverage
- current truth gap
- Save proposal artifacts into
docs/change-proposals/with predictable scope-based filenames. - Add native readback:
- list matching proposals for the current selection
- if useful, also surface proposal linkage in adjacent review or navigation inspector summaries
- once the loop becomes dense enough, promote it into a dedicated native proposal workspace instead of keeping everything buried inside inspectors
- show scope, coverage, evidence, updated time, and richer proposal metadata when available
- prefer native filtering and sorting by scope, status, and coverage before creating a dedicated artifact workspace
- prefer structured metadata such as
Area,Why,Token candidate,Component candidate, andView candidate - tolerate older proposal markdown that only contains
Intent,Targets, and basic acceptance notes - surface typed recovery states for
docs/change-proposals/reload issues such as missing folder, unreadable directory, or unreadable markdown files - support refresh and open/reveal actions
- Keep the markdown shape aligned with
docs/change-marking-contract.md. - Do not couple proposal capture to automatic apply logic in the same slice.
Output Expectations
- proposal save path is deterministic
- matching artifacts are visible from the native inspector
- documentation mentions the repo-aware proposal loop
When not to use it
- →When the task is not extending HumbleStudio's native review flow around markdown change proposals.
- →When coupling proposal capture to automatic apply logic in the same slice.
Limitations
- →The skill preserves a strict boundary between proposal authoring and future write-back.
- →The skill does not couple proposal capture to automatic apply logic in the same slice.
- →The skill tolerates older proposal markdown that only contains `Intent`, `Targets`, and basic acceptance notes.
How it compares
This skill integrates proposal artifact management directly into HumbleStudio's native review flow, providing structured visibility and metadata unlike generic file storage.
Compared to similar skills
humblestudio-proposal-artifact-loop side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| humblestudio-proposal-artifact-loop (this skill) | 0 | 3mo | No flags | Intermediate |
| docs-review | 10 | 7mo | No flags | Beginner |
| claude-md-improver | 21 | 7mo | Review | Beginner |
| backend-to-frontend-handoff-docs | 3 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
docs-review
metabase
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
claude-md-improver
anthropics
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".
backend-to-frontend-handoff-docs
davila7
Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.
readme
sickn33
When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for help with README.md. This skill creates absurdly thorough documentation covering local setup, architecture, and deployment.
doc-gen
phodal
Generate comprehensive documentation from code
generate-verified-docs
quran
Generates audit-grade, hallucination-free documentation from codebase features with full traceability. Use when documenting features, creating technical specs, or generating verified documentation with code references.