「health」の検索結果

Three recap modes - default synthesizes agent health, community growth, and economic activity into a was-it-worth-it verdict; ops recaps what shipped and failed; push ranks push impact.

日本語の概要は準備中です。原文の説明を表示しています。

Autonomous compute-reselling agent on Surplus Intelligence - resells free or low-cost provider compute across Bankr, AWS Bedrock, and Google Vertex (GCP) as one skill. Reads the live market + your cost + your usage, auto-lists your models per enabled provider, and reactively prices each offer to win routing within a cost floor, cap, and health guardrails.

日本語の概要は準備中です。原文の説明を表示しています。

One-pass crypto read - tracked-protocol positions and health plus macro context, with regime take, DeFi verdict, biggest movers, yields, fees, breadth, Fear & Greed, and prediction markets.

日本語の概要は準備中です。原文の説明を表示しています。

Operate managed Aeon instances from memory/instances.json - health-check, dispatch, and status snapshots (control), plus a fleet scorecard of runs, tokens, cost, and reliability (scorecard).

日本語の概要は準備中です。原文の説明を表示しています。

Ambient fleet-health check that surfaces anything worth attention (default), or an on-demand priority brief - the 3 things to focus on, why now, and what moved (var=brief)

日本語の概要は準備中です。原文の説明を表示しています。

Maintain skills wiki health - check links, naming, cross-references, and coverage

日本語の概要は準備中です。原文の説明を表示しています。

Run a full technical and on-page SEO audit on any website or page. Use when the user says "audit my site", "SEO check", "technical SEO review", "site health", "check my SEO", "what's wrong with my site", or provides a URL and asks for SEO feedback.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze website traffic, global rank, engagement metrics, and traffic sources for any domain. Use this skill to evaluate affiliate program websites, compare competitor traffic, assess advertiser strength, or understand where an audience comes from. Triggers on: "analyze traffic for [domain]", "how much traffic does [site] get", "compare traffic between [site A] and [site B]", "is [program] worth promoting based on traffic", "traffic analysis", "website analytics for [domain]", "where does [site] get traffic", "check if [advertiser] is legit", "evaluate [program] website health", "SimilarWeb analysis", "traffic sources for [domain]", "how popular is [site]", "website rank", "domain authority check", "compare affiliate program websites".

日本語の概要は準備中です。原文の説明を表示しています。

Performs comprehensive codebase analysis covering architecture, code quality, security, performance, testing, and maintainability. Use when user wants to audit code quality, identify technical debt, find security issues, assess test coverage, or get a codebase health check.

日本語の概要は準備中です。原文の説明を表示しています。

Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers queries against the corpus, lints the graph for health, and audits in-context human feedback filed from Obsidian or the local web viewer. Use when (1) scaffolding a new knowledge base for any research topic, (2) ingesting articles/papers/PDFs/web pages into raw/, (3) compiling or restructuring wiki articles from existing raw material, (4) answering questions against the wiki and filing durable answers back, (5) running lint passes for dead links / orphan pages / coverage gaps / audit shape, (6) processing human feedback from the audit/ directory and applying corrections. Not for general note-taking, daily journals, or non-wiki Obsidian use.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly, browser heavy. Unions every sitemap each property declares without a browser, builds the candidate set from URLs not already in the indexing ledger, then drives the member's own search performance console to inspect each candidate and request indexing inside an account wide allowance. Spends what is left on sitemap health, which is unmetered. It inspects, requests, and views or submits sitemaps inside that console and does nothing else there, ever, and it never removes a sitemap.

日本語の概要は準備中です。原文の説明を表示しています。

Use when .planning/ looks inconsistent, files are missing, or state seems wrong. Validates .planning/ integrity, reports missing files, bad config, and orphaned plans, and --repair fixes what it finds.

日本語の概要は準備中です。原文の説明を表示しています。

Dung khi can theo doi lien tuc nguoi ta noi gi ve thuong hieu, doi thu va nganh tren mang xa hoi — bo tu khoa giam sat, phan loai sac thai, bao cao tuan va thang, canh bao som, chi so brand health. Kich hoat khi user nhac 'social listening', 'theo doi thuong hieu', 'giam sat mang xa hoi', 'brand monitoring', 'khach dang noi gi ve minh', 'do sentiment', 'co ai nhac ten shop khong', 'canh bao som khung hoang'. Khong dung cho — khung hoang DA XAY RA va can xu ly ngay thi dung skill 66-crisis-playbook; mo xe chien luoc mot doi thu cu the thi dung skill 08-nghien-cuu-doi-thu; doc so lieu ads va web thi dung skill 13-phan-tich-du-lieu.

日本語の概要は準備中です。原文の説明を表示しています。

Dung khi so lieu marketing dang xau va can biet TAI SAO — chan doan theo 5 lop tu tracking, delivery, creative, landing den chat luong audience, roi ra action plan 48h. Kich hoat khi user nhac 'so dang xau', 'CPMess cao qua', 'ROAS thap', 'chan doan root cause', 'tai sao khong ra don', 'ads dot tien'. Khong dung cho — audit CAU HINH tai khoan ads va cham Health Score thi dung skill 21-audit-ads-performance; viet bao cao cho nguoi khac doc thi dung skill 07-bao-cao-marketing; chan doan rieng mot trang thi dung skill 68-cro-audit-trang.

日本語の概要は準備中です。原文の説明を表示しています。

Dung khi can tinh nguoc tu muc tieu doanh thu ra so lead can, CPL toi da va ngan sach phai chi — kem 3 kich ban va nguong healthy tung buoc pheu. Kich hoat khi user nhac 'tinh KPI nguoc', 'CPL toi da la bao nhieu', 'can bao nhieu ngan sach', 'tinh nguoc tu doanh thu', 'muc tieu bao nhieu don', 'break-even ROAS'. Khong dung cho — phan bo ngan sach da co ra tung kenh va thang thi dung skill 61-budget-planning; lap media plan chi tiet theo funnel thi dung skill 54-media-plan.

日本語の概要は準備中です。原文の説明を表示しています。

Use when marketing numbers look bad and the user needs to know WHY — layered root-cause diagnosis across tracking, delivery, creative, landing page, offer, and audience quality, 5-Whys, regional benchmarks for US, EU, SEA, and LATAM, and a 48-hour action plan. Covers dropshipping ROAS and BE-ROAS. Trigger on 'why is CPA so high', 'my ads are not converting', 'ROAS dropped', 'we are burning budget', 'performance is bad this month', 'diagnose the funnel'. Also use when the user pastes a screenshot of numbers with no question attached. Not for — auditing account configuration and scoring health, see `21-ads-audit-global`; writing a report someone else reads, see `07-marketing-report-global`; turning a raw export into insight, see `13-data-analysis-global`.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to monitor what is being said about the brand, competitors, and the category — channels and keywords to track, sentiment scoring, weekly and monthly listening reports, brand health metrics, early crisis detection, and content opportunities pulled from real conversations. Trigger on 'social listening', 'brand monitoring', 'sentiment analysis', 'what are people saying about us', 'track our mentions', 'monitor competitors online'. Also use when the user spotted a bad comment thread and wants to know if it is spreading. Not for — responding to a crisis already underway, see `66-crisis-playbook-global`; competitor strategy teardown, see `08-competitor-research-global`; auditing your own posts, see `39-content-audit-global`.

日本語の概要は準備中です。原文の説明を表示しています。

Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a release_confidence verdict. Use when judging suite value, ROI, or pre-release trust; not for writing or healing tests.

日本語の概要は準備中です。原文の説明を表示しています。

Audit test coverage health, gaps, and QE debt for Jira stories or epics. Produces coverage_analysis_report.md with AC-to-TC heatmap, risk scores, and prioritized action plan. Use when assessing coverage percentage, pre-release readiness, sprint readiness, or identifying missing test cases. Do NOT use for TC creation — use zephyr-test-generation instead.

日本語の概要は準備中です。原文の説明を表示しています。

Audits cross-cutting codebase health, security and maintainability; not a single-change review or specialist audit.

日本語の概要は準備中です。原文の説明を表示しています。

Prepares CI/CD and remote infrastructure, then executes authorized rollouts with health and recovery checks; not standalone local container packaging.

日本語の概要は準備中です。原文の説明を表示しています。

Elixir/Phoenix deployment patterns — Dockerfile, fly.toml; Use when configuring Fly.io, Docker, CI/CD, health checks…

日本語の概要は準備中です。原文の説明を表示しています。

Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.

日本語の概要は準備中です。原文の説明を表示しています。

Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.

日本語の概要は準備中です。原文の説明を表示しています。