code-yeongyu/oh-my-openagent / packages/shared-skills/skills/ulw-research
ulw-research
UnverifiedRuns maximum-saturation research with a cooperating team, claim-graph gating, and a cited, QA'd deliverable. Use when the user explicitly asks for research or a deep investigation, including any 'ulw' research wording.
scripts/tests/fixtures/bad-report.html
View on GitHub<!doctype html>
<html lang="ko">
<head>
<meta charset="utf-8">
<title>Static gate fixture: every static defect once</title>
<style>
:root { --bg: #f7f5f0; --fg: #1f1d1a; --accent: #2f6f4f; }
body { background: var(--bg); color: var(--fg); font-family: "Nanum Myeongjo", serif; }
.note { color: #123456; }
</style>
</head>
<body>
<main>
<h1>분기별 배포 지표 점검 보고서</h1>
<section>
<h2>배포 지표가 흔들린 분기</h2>
<p>이번 분기에는 배포 파이프라인을 두 번 바꿨고, 그 과정을 기록으로 남겼어요 [S1].</p>
<p>매출이 12.5% 증가했다.</p>
<p>The rollout finished early — nobody expected that [S1].</p>
<p>A quick win–loss review followed [S1].</p>
<p>Launch day went well 🚀 [S1].</p>
<h3>Summary</h3>
<h3>This subsection heading keeps going far past any sensible single line of text</h3>
<img src="data:image/png;base64,iVBORw0KGgo=" alt="unwrapped chart" width="480" height="240">
<figure>
<svg width="480" height="240" viewBox="0 0 480 240"><rect x="0" y="0" width="40" height="120" fill="#2f6f4f"/></svg>
<figcaption>Blank chart [S1]</figcaption>
</figure>
<figure>
<svg width="480" height="240" viewBox="0 0 480 240"><title>Weekly deploys</title><text x="4" y="230">0</text><text x="4" y="20">10</text><text x="200" y="236">Deploys</text></svg>
<figcaption>Two ticks only [S1]</figcaption>
</figure>
<figure>
<img src="assets/missing-figure.png" alt="lost asset" width="480" height="240">
<figcaption>Lost asset [S1]</figcaption>
</figure>
<figure>
<img src="data:image/png;base64,iVBORw0KGgo=" width="480" height="240">
<figcaption>Image without alt text [S1]</figcaption>
</figure>
</section>
<section>
<h2>팀 구성은 그대로였다</h2>
<p>팀 구성은 분기 내내 바뀌지 않았고, 새로 합류한 사람도 떠난 사람도 없었어요. 역할 분담도 그대로여서 배포 담당자는 여전히 한 사람이었고, 리뷰는 돌아가면서 맡았습니다. 회의 방식과 문서 양식도 이전 분기와 같았어요. 그래서 이 절에서는 사람 쪽 변화가 원인이라고 보기 어렵다는 점만 적어 둡니다.</p>
</section>
</main>
</body>
</html>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |