polish
Polish Interfaces Before Release
Small interface issues can make complete work feel unfinished. This skill guides a final pass across visual detail, interaction states, accessibility, responsiveness, and code cleanliness.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "polish" from https://skillstore.io/skills/pbakaus-polish.md and its manifest at https://skillstore.io/api/skills/pbakaus-polish/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "polish". Polish the settings page before release.
Expected outcome:
A prioritized review covering spacing inconsistencies, missing focus states, unclear labels, mobile layout issues, and final cleanup tasks.
Using "polish". Check the checkout flow for final quality.
Expected outcome:
A release-ready checklist with interaction states, error handling, loading feedback, accessibility concerns, and responsive issues to verify.
Using "polish". Review this dashboard for polish gaps.
Expected outcome:
A concise quality pass covering table density, chart labels, empty states, keyboard navigation, visual hierarchy, and copy consistency.
Security Audit
SafeThe static findings are false positives caused by Markdown inline code and design terms such as grid and responsiveness. I found no evidence of command execution, system reconnaissance, network reconnaissance, prompt injection, data exfiltration, or malicious intent in SKILL.md.
Risk Factors
⚙️ External commands (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/pbakaus-polish/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/pbakaus-polish?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/pbakaus-polish?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/pbakaus-polish/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/pbakaus-polish.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
pbakaus. (2026). polish security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/pbakaus-polish/audits/4BibTeX citation
@techreport{pbakaus-pbakaus-polish-2026,
author = {pbakaus},
title = {polish security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/pbakaus-polish/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "polish security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "pbakaus"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/pbakaus-polish/audits/4"
identifiers:
- type: other
value: "skillstore:pbakaus-polish:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a Feature for Release
Run a structured final pass before shipping a completed interface.
Check Implementation Fidelity
Compare the built experience with intended spacing, typography, states, and responsive behavior.
Triage Final Quality Work
Identify the most visible polish issues when release time is limited.
Try These Prompts
Use the polish skill on the current feature. Focus on visible spacing, alignment, copy, and obvious interaction issues.
Use the polish skill to review mobile, tablet, and desktop behavior. Include contrast, focus states, labels, alt text, and touch targets.
Use the polish skill to inspect loading, empty, error, disabled, success, hover, focus, and active states for this workflow.
Use the polish skill to create a prioritized release polish pass. Separate blocking issues, high-impact refinements, and optional improvements.
Best Practices
- Use it after core functionality is complete and before final release review.
- Test the same workflow across supported viewports, themes, and interaction states.
- Prioritize issues by user impact, release risk, and time available.
Avoid
- Do not use it to polish unfinished features with unresolved product behavior.
- Do not apply visual changes without retesting the affected workflow.
- Do not perfect one small area while leaving broad consistency issues unresolved.