メニュー
Build an interactive Agentic-App (output.html) that the user sees next to the chat and that can send prompts back into the conversation. Use when the user asks for a page, dashboard, form, report, or any visual/interactive result.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Guides agents through isolated Git worktree setup, lifecycle commands, process cleanup, and per-worktree local development state. Use when creating, starting, stopping, inspecting, cleaning up, or troubleshooting Git worktree development environments or when a repository includes a worktree lifecycle CLI.
Continuously watch and fix release main CI until the branch is fully green and verified working. Use when asked to babysit CI, babysit CI release, monitor release main, run /loop for CI, run /goal until checks pass, or keep iterating until release main is green.
Fix flaky tests by repeatedly running the suite, collecting intermittent failures, and proving stability. Use when asked to fix flaky tests or require repeated/consecutive green test runs.
Manage LinkedIn messaging, profiles, posts, connections, and company pages via Unipile. Use for networking, content publishing, and lead engagement.
Scoped commit workflow with a bundled committer script that prevents accidental broad staging. Use when the user asks to commit, commit all, create a git commit, or handle commit-time staging in this repository.
Systematically QA a web application like a real user, triage issues by severity, fix scoped bugs when asked, verify fixes with evidence, and report ship readiness. Use when asked to QA, test a site or app, find bugs, test and fix, or check whether a feature works.
| name | agentic-app |
| description | Build an interactive Agentic-App (output.html) that the user sees next to the chat and that can send prompts back into the conversation. Use when the user asks for a page, dashboard, form, report, or any visual/interactive result. |
An Agentic-App is a single self-contained HTML file you write to /app/output.html. Bap collects it automatically (you do not need to mention it in your answer) and renders it beside the conversation in a sandboxed iframe. Buttons and forms inside the page can send a prompt back into the conversation — the prompt becomes a real user message, exactly as if the user had typed it.
/app/output.html (case-sensitive basename output.html).allow-scripts allow-forms only: your script cannot make network calls to Bap, cannot read cookies, and cannot navigate the parent page. The ONLY channel back to Bap is the prompt protocol below.Post a message to the parent window:
parent.postMessage(
{ type: "bap:agentic-app-prompt", version: 1, prompt: "Send the weekly email to the team" },
"*",
);
prompt must be a non-empty string. It is sent as a user message with the conversation's existing settings; you cannot attach files or change the model.window.addEventListener("message", (event) => {
const data = event.data;
if (!data || data.type !== "bap:agentic-app-prompt-result") return;
// data.status is "sent" or "rejected"
// on rejection, data.reason may be "rate_limited", "no_user_activation", or "invalid"
});
sent means the prompt is now a user message in the conversation (a new agent run starts, or it queues behind the current one). rate_limited means slow down — disable the button briefly. no_user_activation means the send did not come from a real user interaction.<!doctype html>
<html>
<body>
<button id="send">Send the weekly email</button>
<script>
const btn = document.getElementById("send");
let ackTimer = null;
btn.addEventListener("click", () => {
btn.disabled = true;
btn.textContent = "Sending…";
parent.postMessage(
{ type: "bap:agentic-app-prompt", version: 1, prompt: "Send the weekly email" },
"*",
);
// Recover if no ack arrives (e.g. rendered in a read-only view).
ackTimer = setTimeout(() => {
btn.textContent = "Try again";
btn.disabled = false;
}, 3000);
});
window.addEventListener("message", (event) => {
const data = event.data;
if (!data || data.type !== "bap:agentic-app-prompt-result") return;
clearTimeout(ackTimer);
if (data.status === "sent") {
btn.textContent = "Sent ✓";
} else {
btn.textContent = "Try again";
btn.disabled = false;
}
});
</script>
</body>
</html>
Build prompts dynamically from form values when useful (for example, interpolate a recipient and subject the user typed into the page), but always send them from a click or submit handler.