The project's episodic memory: a timestamped ledger of rules paid for with real outages and near-misses, one entry per incident. Load WHENEVER you write or review a DB migration or schema change, touch deploy/release workflows (.github/workflows/deploy-*, promote.yml, vercel config), plan a promote/release, respond to a prod incident, or when another skill references a learning. ALSO load after resolving any incident or near-miss: it must leave a new ledger entry in the same session.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Every rule this repository paid for with downtime or a near-miss is one entry in a timestamped, append-only ledger. The ledger is the full history, in the order it was learned.
| Path | What it is |
|---|---|
MEMORY.md | The index. One line per entry, newest first: recorded time (UTC) and the rule. Generated. |
entries/<YYYY-MM-DDTHHMMSSZ>-<slug>.md | One entry. The filename timestamp is when it was recorded. |
scripts/new-entry.sh | Starts a new entry stamped with the current UTC time and rebuilds the index. |
scripts/index.sh [--check] | Rebuilds MEMORY.md from entries/, or fails if it is stale. |
Entries recorded before 2026-09-25 were split out of the old single-file register. Their
recorded time is the commit that first wrote them (commit in the frontmatter).
grep -i '<keyword>' .agents/skills/learnings/MEMORY.md
grep -ril '<keyword>' .agents/skills/learnings/entries/
migration, CONCURRENTLY, deploy-dev, promote,
wake, Stop, gateway, preview, the file or route name.Done when every entry that names the surface you touch has been read.
Record in the same session. An incident that leaves no entry is not finished.
.agents/skills/learnings/scripts/new-entry.sh "<the rule, as an imperative>" [incident-date]
MEMORY.md in the same commit.Done when scripts/index.sh --check exits 0 and the entry is committed.
supersedes: <entry filename> in its frontmatter and state what changed.recorded in the frontmatter matches the
filename. It is the time of recording, never the incident date. The incident date goes
in incident_date.MEMORY.md is generated. Run scripts/index.sh after any entry change. It merges
with git's union driver, so two branches that each add an entry do not conflict. A
GitHub squash merge keeps a branch's index line where the branch put it, so the order
on main can drift until the next index.sh run. index.sh --check and
tests/unit/learnings-ledger.test.ts compare the lines, not their order: they fail on a
missing, extra, or retitled index line, or a malformed entry.PR #1234).entries/ is the only incident record.
Do not write a separate incident, RCA, spec, or runbook file, and do not link one.
The repository has no docs/ tree, and the pre-commit hook rejects new files under it.<session_id>.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Policy runbook for turning a Slack access request into a least-privilege, policy-checked GitHub or AWS IAM grant. Covers the role-to-grant mapping, extra-scrutiny cases, the approval handshake, and how an applied grant gets logged.
日本語の概要は準備中です。原文の説明を表示しています。
Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.
日本語の概要は準備中です。原文の説明を表示しています。
Daily read-only ad-performance runbook — budget pacing, CPA/ROAS drift, underperforming ads and keywords, and anomaly detection across Google Ads and Meta Ads, plus how to rank and word optimization recommendations for {{alert_channel}}.
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
日本語の概要は準備中です。原文の説明を表示しています。
Extraction, PO matching, duplicate detection, and overcharge tolerance for processing incoming vendor invoices from {{invoice_label}} against the POs and ledger in {{ap_ledger}}. Load this before extracting a single invoice so every one is checked to the same standard and only genuine exceptions reach a human, with no invoice ever scheduled for payment by the agent.
日本語の概要は準備中です。原文の説明を表示しています。
Daily brand-mention monitoring loop for {{brand_terms}}. Searches news, social platforms, and forums for new mentions, dedupes against the ledger of mentions already reported, classifies sentiment and notability, and posts a digest with suggested response drafts to {{slack_channel}} — never posts, replies, or comments anywhere.
日本語の概要は準備中です。原文の説明を表示しています。