'quote' 검색 결과

Proposes the instrumentation and control content a P&ID adds to an accepted PFD process model: instruments drawn carried over as facts, measurement points and control loops the control philosophy requires, tag structure per the project instrument numbering procedure, system interfaces, and alarms, interlocks, trips and fail actions as quoted. Never assigns safety functions, ranges or setpoints. Use when the user asks to "run the instrumentation and control enrichment", "add the instrument section to the P&ID draft", "list the control loops the philosophy requires" or "carry the PFD instruments into the P&ID" after the piping section. Do not use for safety flags, SIL or trip classification, use process-safety-flags instead; do not use to assign tag numbers, use tagging-and-numbering. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audits a website codebase and makes code changes so AI engines (ChatGPT, Claude, Perplexity, Google AI Overviews) can better discover, parse, quote, and cite the site. Covers structured data, content structure, technical signals, and freshness.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Creates data visualizations (charts, graphs, tables) optimized for AI engine parsing and citation. Produces inline SVG/HTML with text summaries, data tables, and JSON-LD so AI engines can quote the data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prose final-pass editor for GitHub issue bodies, pull request bodies, release notes, README/docs changes, public comments, and user-facing explanations. Use when Codex drafts or revises substantial prose that will be published or committed, especially when the user asks to polish, de-slop, make it less AI-written, improve a PR/issue body, or prepare docs text; do not use for ordinary code implementation, debugging transcripts, logs, quoted text, command output, API names, or Chinese conversational replies unless explicitly requested.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

End-to-end vendor procurement workflow orchestrating RFQ creation, email sending, vendor response tracking, and client-facing estimate generation. Use this skill when managing the full quote-request-to-client-estimate pipeline, coordinating between vendor-rfq-creator and vendor-estimate-creator skills with email automation and status tracking.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Knowledge pack synthesized from JSP 376 Defence Acquisition Safety Policy V1.1 (April 2024, Ministry of Defence, Open Government Licence v3.0): acquisition safety requirements, safety artefacts, and their application across the standard acquisition lifecycle. Covers the policy frame and legislative baseline, SRO and User responsibilities, safety management and safety requirements, test and evaluation and the safety case, supervision and approvals decision support, and the seven lifecycle phases. SCOPE LIMITS: single-source (JSP 376 V1.1); MOD policy and guidance, not statute; builds on JSP 815 and cites JSP 655, neither reproduced here (use jsp-815 for the SMS); Chapter 4 (Non-Standard Acquisition) is unpublished in V1.1 and is not in this pack; no DEF-STAN text (Def Stan 00-056 is named, not quoted); no other JSP reproduced. Reconstructed reference notes, not MOD guidance, and no official status.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stock quotes, history, search, compare, crypto via Yahoo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "build a media list for my launch", "write a launch press release", or "pitch press under embargo"; produces a three-tier media and analyst list (Tier 1 exclusive candidates, Tier 2 vertical press, Tier 3 communities and newsletters), an embargo pitch timing skeleton keyed to the launch-registry date, a press-release draft in standard structure with no fabricated quotes or numbers, and an analyst briefing outline. Not for press-kit assets — use launch-asset-packager; not for follow-up sequence mechanics — use outreach-manager; not for post-launch news-echo monitoring — use launch-monitor. 媒体名单/禁运期pitch/新闻稿/分析师简报

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "triage launch feedback", "cluster reviews, comments, and board posts into themes", or "set up a you asked, we shipped loop"; produces a feedback theme digest (frequency, severity, representative quotes per theme), an open→planned→started→completed/declined status loop with duplicate-merge and notification rules, shipped-change announcement material, and a compliant social-proof harvest protocol (never incentivized store reviews). Not for repurposing or amplifying the harvested proof — use content-amplifier; not for executing testimonial outreach threads — use outreach-manager. 反馈分诊/状态环/社证收割/评测合规

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "map what our buyers believe", "capture the objections we keep hearing", or "find the switching forces that move the beachhead"; produces a belief map of the beachhead — held beliefs and mental models, the recurring objections and their reframes, and the JTBD four forces (push of the problem, pull of the new, anxiety of switching, habit of the present) — each item sourced from interviews or win-loss notes (User-provided) and labeled Measured / User-provided / Estimated, with any unverified quote or comparative claim marked "[needs source]" and routed to the claims candidates, never adjudicated here. Not for demographic or persona profiling — use audience-mapper; not for the positioning canvas — use positioning-truth-tracer. 受众信念/异议地图/切换四力/流失语言

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MSBuild property definition patterns: conditional defaults, composition/concatenation, path normalization, trailing slash handling, TFM detection helpers, and property evaluation order. Only activate in MSBuild/.NET build context. USE FOR: diagnosing and fixing MSBuild property definition issues in .props or .csproj files, reviewing and fixing shared property configuration anti-patterns, fixing DefineConstants or NoWarn being overwritten instead of appended, fixing unconditional property assignments that prevent project-level overrides, fixing unquoted conditions that fail when properties are empty, fixing hardcoded paths that break cross-platform builds, setting property defaults that can be overridden, understanding property evaluation order and last-write-wins semantics. DO NOT USE FOR: props vs targets placement (use directory-build-organization), item operations (use item-management), target structure (use target-authoring), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Catalog of MSBuild anti-patterns with detection rules and fix recipes. Only activate in MSBuild/.NET build context. USE FOR: reviewing, auditing, or cleaning up .csproj, .vbproj, .fsproj, .props, .targets, or .proj files. Each anti-pattern has a symptom, explanation, and concrete BAD→GOOD transformation. Covers Exec-instead-of-built-in-task, unquoted conditions, hardcoded paths, restating SDK defaults, scattered package versions, and more. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake, etc.), project migration to SDK-style (use msbuild-modernization).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stock quotes, price history, financial news, and analysis

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Search past WhatsApp/chat conversations stored in the audit log PostgreSQL database. Use when the user asks about past conversations, what was discussed, what someone said, finding a specific message, or referencing previous discussions. Also use to reply to or quote specific past messages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Check invoices and receipts line by line against your offers and list what matches, what differs and what has no offer. Nothing is paid or sent. Use for "check my invoices", "match invoices to offers", "does this invoice match the quote".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage files and folders on the Unique AI Platform using the unique-cli command-line tool. Use when the user asks to upload, download, delete, rename, list, find, restore versions, list versions, look for, or organize files and folders on Unique, or to read / view / quote the text contents of a known file (optionally by page or page range, e.g. "what's on page 5?", "read pages 10-12"), or when working with scope IDs (scope_*) or content IDs (cont_*). IMPORTANT: When a user says they are "looking for a file" or wants to "find a file", they typically mean locating it within the Unique AI Platform knowledge base — not on the local filesystem. Use this skill to browse and list folders/files on Unique to help them find it. This is also the preferred approach for locating Excel (.xlsx/.xls), CSV (.csv), and image files, as these file types are not full-text indexed and cannot be found via vector/full-text search.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

元のポストに自分のコメントや意見を加えて引用リポストするための内容を生成。「引用リポスト」「引用ツイート」などで使用。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fetch a URL and save the body to a temp file so you can pipe it through rg / jq / awk instead of dumping the whole page into the conversation. Use this whenever a user gives you a URL to read - articles, docs, PRs, gists, README files, blog posts, anything HTTP. Returns a path on disk; the agent then greps the path for the relevant section and quotes only what matters. Strongly preferred over the built-in webfetch tool when (a) the page is more than a few KB, (b) the user wants to find a specific phrase / table / code block on the page, (c) you need to keep the long page out of context, or (d) you want to inspect raw HTML alongside rendered markdown. Triggers: 'fetch', 'fetch this URL', 'fetch and save', 'fetch the page', 'pull this', 'grab this article', 'read this URL', 'read the docs at', 'mirror this page', 'page is too long', 'save the page so I can grep it', 'put it on disk so I can rg', 'cache this URL'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

当使用者给出「说话人名字 + 说话内容 + 主色」，说"做一张车队无线电那种语录卡"、"生成 XX RADIO 的图"、"把这句话做成无线电字幕卡"、"照那个红色波形的格式来一张"时使用。产出单文件 HTML，800×1000 竖版：顶部是名字（主色）加 RADIO（白色）的粗斜体标题、中间一条主色音频波形加通栏横线、下方是主色粗斜体全大写的引号语录、底边一条主色横条，底色固定为近黑。使用者没给图标就不放图标。不生成任何车队或厂商的徽标，不伪造真人说过的话。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detect privilege escalation attempts including token manipulation, UAC bypass, unquoted service paths, kernel exploits, and sudo/doas abuse across Windows and Linux.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment ("split test demo", "the File engagement boost experiment", "onboarding retention test", "landing page hero experiment", "pricing experiment"), describes it loosely ("the signup experiment", "my pricing test", "the one with the new checkout"), uses a relative reference ("latest", "most recent", "the one I created yesterday"), filters by status (running, draft, stopped, archived), or otherwise refers to an experiment by anything other than its concrete ID.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

一句话主导的社交卡 — 论点 / 引言 / 原则 / 关键问句 / 一句话洞察占满版心，配 source / 章节标签 / 边注 / 三个锚点。必须按语义断行（不靠自动 wrap），至少一个锚点防止 floating。触发："做个引言卡 / 论点卡 / 金句卡 / 原则卡 / hero 问句卡"。NOT 长段落伪装成引言，NOT 空洞鸡汤口号，NOT 居中文字无任何锚点结构。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.