Loading...
Loading...
Found 505 Skills
Resolve current external facts, official documentation, library behaviors, and API contracts against primary sources before implementation. Use when consulting library documentation, checking breaking changes, investigating external APIs, or verifying framework versions — even if the user does not explicitly say "fable-research" (e.g. "check the latest docs", "what is the API for X in version Y", "look up SDK specs", "verify library support"). Do NOT use for repository-local code exploration (use fable-discover) or for writing implementation code directly (use fable-tdd or fable-execute).
Create, review, and manage first-class goal artifacts that turn a broad ambition into an externally verifiable outcome. Goals are optional, long-lived workflow artifacts stored at goals/<slug>.md. They own intent, a validation contract, lifecycle, concise review evidence, and linked work. Use when the user wants to set a goal, review a goal, pause or reactivate a goal, achieve or abandon a goal, or change what a goal means. Not for specs, plans, memory, or checkpoints.
Use when an approved workspace spec needs an execution-ready implementation plan with ordered, verifiable steps. Specs are mandatory: this skill consumes design decisions, verifies that the spec still matches the codebase, and writes the repo-native plans/ artifacts. Inherits optional goal provenance; see loam::setting-goals.
Research workspace context, APIs, implementation options, or external evidence before planning. The terminal artifact is always a spec at specs/<slug>.md; a plans/research/<slug>.md memo is optional supporting evidence when substantial investigation was needed. Accepts an optional goal path for provenance; see loam::setting-goals.
Builds an app, site, bot, or feature end-to-end from a dictated idea — requirements, briefing, spec, tickets, subagents, review, acceptance — with a live dashboard, for users who expect a finished result without reviewing specs or code. Starts only on /autopilot; a bare /autopilot resumes an interrupted run.
Hub MỘT TÊN cho dây chuyền sản xuất kiểu Ralph (GH#15): biến tài liệu thô của user thành sản phẩm qua 5 mode — `/br interview` (đọc folder raw/ → đối chiếu bộ specs chuẩn S1–S10 → sinh bộ câu hỏi hỏi-bù dạng HTML xem trước + MD điền, cho phép lens chuyên gia điền thay mục chưa chắc), `/br compile` (answers → BR.md có clause_id + bảng "Giả định đang gánh"), `/br slice` (BR → frames nhỏ gắn chặt code, gác bằng frame-lint), `/br run <frame>` (mỗi frame chạy loop-runner có 6 phanh + dry-run + người gác · sau frame xanh TỰ chạy QC tất định 0-token), `/br qc` (audit senior 4-mục: /qc-code soi code + /qc-uiux soi UI/UX qua engine visual-qa), `/br status` (trang line-status.html tất định: frame nào chạy/kẹt/xong + truy ngược lỗi→frame→clause). Gọi khi user nói "br", "interview", "phỏng vấn yêu cầu", "soạn BR", "slice frame", "chạy frame", "qc frame", "audit ui mockup", "trạng thái dây chuyền", "ralph pipeline", hoặc invoke /br. User chỉ mô tả PHẠM VI, không cần nhớ lệnh con.
Writes, migrates, and fixes OpenAPI specs for Google Cloud API Gateway. Use when converting an OpenAPI 2.0 (Swagger) spec to OpenAPI 3.x, writing a new OpenAPI 3.x spec, or fixing a failed "gcloud api-gateway api-configs create", such as "extension is only supported in OpenAPI 2.x". Also use when quotas set with x-google-quota are never enforced, or when a backend receives path parameters as query parameters. Don't use for adding or debugging MCP tools (use api-gateway-mcp-server), backend lockdown or HTTP 429 tuning (use api-gateway-backend-security-and-rate-limiting), Cloud Endpoints, Apigee, or GKE Gateway API.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Create and update living specs and code walkthroughs with diffmap. Use when planning work, implementing from a spec, updating a spec, or explaining code changes.
The Pinterest SEO / search-ranking skill -- the keyword layer that pairs with pinterest-pin-design's visual. Use when someone wants pins to rank in Pinterest search, needs keyword research, or wants keyword-optimized pin titles/descriptions/boards. Pinterest is a visual search engine where keywords and relevance rank you, not followers. Uses the FOUND framework. Reads brand-profile + the pin's destination first. The agent researches real queries (autocomplete + Guided Search + Trends; never fabricates volume), writes the keyword-led title + a natural description (no stuffing), specs the on-pin overlay keyword, and advises boards + link. WoopSocial publishes the pin's title + description + board + link; profile/bio, board setup, alt text, Rich Pins, and Trends/Analytics stay native/human. No stuffing; Pin->Board->Page must match; fresh pins, not dupes. Distinct from pinterest-pin-design (the visual), pinterest-growth (the strategy), and social-seo (cross-cutting search).
Provider-independent FFmpeg finishing workflow for AI agents preparing generated or edited media deliverables. Use when finalizing images, image sequences, video, audio, captions, overlays, social/export variants, checksums, manifests, delivery specs, and QA with ffmpeg/ffprobe, including transcode versus stream-copy decisions, scaling, frame-rate handling, color metadata caution, loudness normalization, subtitle burn-in or sidecars, concat/trim, GIFs, batch variants, and reproducible command reporting.