「fts」の検索結果

Reviews a proposal, business case, deck or plan in character as a Chief Marketing Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to specific passages, marketing risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CMO review", "pressure-test the positioning", "what would a CMO say about this", "challenge the launch plan" or "check the messaging and audience". Do not use for price economics, margins or payback, use cfo-reviewer instead; for sales pipeline mechanics, use cro-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Information Security Officer archetype and returns a DRAFT review with a verdict, findings cited to specific passages, security and compliance risks and the five interrogation questions a real CISO would ask. Use when the user asks to "run a CISO review", "pressure-test the security of this plan", "what would our CISO say about this" or "check the privacy and third-party risk". Do not use for contract, liability or regulatory-interpretation reviews, use general-counsel-reviewer instead. Drafts for human review; never approves, authorises or signs off.

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

Builds a self-contained single-file HTML project dashboard (status banner, milestones table, risks heat list, decisions log, links) from the project tracker files the user attaches, pastes or holds in configured knowledge sources, and returns the complete HTML source in chat ready to save as dashboard-project-date.html. Use when the user asks to "build a dashboard for this project", "make a status page I can pin in the team channel", "give me an HTML overview of milestones, risks and decisions", "refresh the project dashboard from the tracker" or "turn these tracker files into a one-page visual summary". Do not use for creating or updating the tracker files or for the written weekly status report, use project-status-tracker instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck, pricing plan, go-to-market plan or forecast in character as a Chief Revenue Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to exact passages, revenue risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CRO review", "pressure-test the revenue plan", "what would sales leadership say about this" or "challenge this forecast". Do not use for partnership, deal-structure or market-positioning reviews, use cbo-reviewer instead; for the finance seat use cfo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Proposes tag and number structures for the new lines and instruments in a P&ID draft according to the project's numbering procedures, checks every tag extracted from the PFD against the quoted procedure format, and lists cross-section identifier mismatches and the registry checks a human must run. Never invents a numbering convention, never alters a PFD tag and never assigns a sequence number the procedure reserves for the registry. Use when the user asks to "run the tagging and numbering section", "check the tags against the numbering procedure", "propose the tag structure for the new lines and instruments" or "list the registry checks before validation" after the process safety flags. Do not use for validating the four sections, use validation-and-review-package instead; do not use for instrument content, use instrumentation-and-control-enrichment. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT data dictionary from a schema export, table definition, sample rows or a partial existing dictionary: one row per field with the name as stated, type as stated or observed, meaning quoted from the documentation supplied, owner, allowed values, and UNKNOWN wherever no source defines the field, plus a gap list for the data owner. Never infers a definition from a column name. Use when the user asks to "build a data dictionary for this table", "document these columns", "what does each field mean", "turn this schema export into a dictionary" or "fill in the field definitions from these documents". Do not use for profiling values or finding patterns in the data, use dataset-insight-pack instead; for metric definitions, use kpi-definition-sheet; for logging data defects, use data-quality-issue-log. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT board paper skeleton from the sponsor's inputs: purpose, recommendation as the sponsor states it, options including do nothing, risks, financials exactly as provided, authority to decide and the decision sought, with every claim tagged evidenced, asserted or UNKNOWN so the sponsor sees what still needs support. Use when the user asks to "draft a board paper", "structure the committee paper", "prepare the decision paper for the investment committee", "skeleton the board memo" or "what goes in the paper for the audit committee". Do not use for a pre-read or briefing pack with no resolution sought, use executive-briefing-pack instead; to record a decision already taken in a discussion, use decision-memo-builder. Drafts for human review; never approves, authorises or signs off.

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

Analyzes changes since last release and drafts them directly into the project's CHANGELOG.md. Use when users requests 'update the changelog' or 'prepare changelog release notes'

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

Full-text keyword search across every conversation at once (Telegram, Facebook, ChatGPT, Claude, notes, transcripts) over a local BM25/FTS5 catalog: instant, zero tokens, with snippets and chat-title hits. The exact-words lane, complementary to semantic search. Triggers: "/search <words>", "where did I write about <X>".

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

Review content quality before anything is shown or sent (vault notes, outgoing drafts, dedup merges, service files) and return an explicit pass, fail or manual-review verdict. The counterpart of a post-build test gate: that one asks whether the build works, this one whether the writing is fit to show. Triggers: "/taste-check <path|text>", "/taste", "check this note".

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

Mine the day's sessions for the owner's intentions, cluster them into distinct ones, store them, and write two or three detailed posts with an explicit ask per channel, plus a loop tracking who answered. Drafts only. Triggers: "/intention", "mine today's intentions", "intention posts".

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

Split one source post into tier-sized drafts (teaser, main social post, longread, technical dev-log) with cross-links downward and a canonical link back to the repository. Draft-first: publishes nothing itself. Triggers: "/episode", "/adapt", "adapt this post", "make an episode".

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

Scan recent agent sessions for content-worthy moments and capture them as drafts in a publishing funnel, publishing nothing. Zero-token detector, then a taste judge, then capture. Triggers: "/content-mine", "mine sessions for content", "what in our sessions deserves a post".

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

Work the comments under published posts in one pass: list unanswered ones, reply only where a reply is genuinely expected (at most three per pass), name top commenters as warm-DM candidates, and prepare reply drafts on approval. Triggers: "/comments", "unanswered comments", "who is commenting".

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

Agentic design-to-build pipeline that turns a Figma design into a built WordPress site using the Figma MCP server (read side) and the Elementor MCP server (write side) attached as MCP Apps on an NV oOS assistant. Covers the 7-stage pipeline (Scope → Read → Plan → Tokenize → Build → Verify → Handoff), the normative stage rules (get_design_context first, tokenize before build, drafts only, never publish, Figma read-only), the build-manifest contract (schema + example in reference/build-manifest.md), the design-file contract (frame/section/variable naming in reference/design-file-contract.md), assistant wiring (figma + elementor MCP Apps, OAuth + application passwords, host allowlist), safety rules, and troubleshooting. Use when asked to build or create a site, page, or landing page from a Figma design, to wire Figma MCP or Elementor MCP for design-to-build work, to approve or produce a build manifest, or to debug a failed design-to-build run.

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

Gmail skill for sending, reading, searching, labelling, and managing email via the gws CLI. Covers messages, threads, labels, drafts, filters, and inbox management.

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

Autonomous DevSecOps & FinOps Guardrails. Orchestrates Gemini 3 Flash to audit Linux Kernel patches, Terraform cost drifts, and K8s compliance.

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

Use when the user asks to "package the launch assets", "build a press kit", or "prep the store listing and go-live checklist"; produces a tier-scoped launch asset manifest with production status — a press kit spec (factsheet, description, history, features, videos, images, logo and icon, awards, contact), demo script and screenshot specs, a launch FAQ, dual-store listing metadata drafts against the official character budgets (per App Store Connect / Play Console documentation), and a technical go-live checklist manifest (robots flip, sitemap, OG tags, analytics verification — execution stays with technical-seo-checker and serp-markup-builder). Not for the message copy itself — use message-house-builder or content-writer; not for landing page UX — use landing-optimizer; not for keyword research beyond the store surfaces — use keyword-research. 发布资产打包/press kit/商店listing规格/上线检查清单

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

Use when the user asks to "write SEO content", "draft a blog post / landing page", "update outdated content", or "fix traffic/ranking decay"; two modes — new drafts pages with keywords, headers, snippets, and evidence boundaries; refresh scores decay, prioritizes update work, and produces a republish plan with GEO guidance. Not for AI-citation/GEO readiness scoring — use geo-content-optimizer; not for publish-gate scoring — use content-quality-auditor. SEO文章写作/内容更新/排名恢复

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

Create authorized presenter, avatar, and UGC-style video drafts with explicit voice, likeness, consent, and synthetic-media handling.

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

Turn brand context and a social brief into platform-aware copy, storyboard, reference frames, and video drafts without publishing them.

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

Use when the user wants to capture a real repo's working patterns as a reusable skill — analyzes the local git log and diffs the agent runs itself and drafts a new SKILL.md describing the team's coding patterns, into a scratch/output path the user names. Never overwrites an existing skill.

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

Build and run the owner's self-branding system in a structured way across LinkedIn, Substack, dev.to, X, profile rewrites, recurring series, and comment strategy. Use when the owner asks for positioning, a branding plan, profile updates, content drafts, a publishing sequence, comment ideas, or help maintaining a consistent public voice. Optimize for operator credibility: specific experience, defensible numbers, concrete artifacts, and category ownership.

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

Query Solana wallets, tokens, txs, and NFTs in USD.

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