「ngs」の検索結果

Prepare structured briefings for meetings with legal relevance and track action items. Use when prepping legal meetings.

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

How App Store ratings actually behave — per-storefront isolation (your US stars show nowhere else), the never-reset rule, phased release + manual release as rating protection, and where prompting/replying fit. Use when planning ratings strategy for new markets, considering a ratings reset, setting release options, or diagnosing "why is my rating missing in country X."

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

Calculate realistic affiliate earnings projections before committing to a program. Use this skill when the user asks about affiliate earnings, projecting income, calculating commissions, estimating how much they can make, comparing program payouts, or says "how much can I make promoting X", "calculate my affiliate income", "is this commission worth it", "how long to first $1000", "compare earnings between programs", "traffic to income calculator", "what conversion rate should I expect", "earnings estimate for affiliate program", "how many sales do I need".

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

Use this skill before answering or editing whenever an MSTest v1/v2 project is being upgraded or repaired for v3. Triggers include QualityTools assembly references; MSTest.TestFramework/TestAdapter 1.x-2.x; "upgrade to MSTest v3"; comparing v1 and v2 migration paths; choosing MSTest or MSTest.Sdk; CS0411/CS1503 after a v3 package bump; DataRow type mismatch, MSTEST0014, or "Test data doesn't match method parameters"; .testsettings/LegacySettings to .runsettings; timeout changes; and net5.0 or other dropped v3 TFMs. Still use it when packages say 3.x but migration source errors or legacy settings remain. Preserve VSTest/MTP. Do not use for a clean v3 project, v3-to-v4, framework conversion, or runner-only migration.

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

Use when ready to document findings, generate a report, or summarize binary analysis results. Compiles analysis findings into structured reports - correlates facts from triage/static/dynamic phases, validates hypotheses, generates documentation with evidence chains. Keywords - "summarize findings", "generate report", "document analysis", "what did we find", "write up results", "export findings"

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

Use when processing, summarizing, or extracting insights from meeting notes in the Obsidian vault. Triggers on "summarize meetings", "process meetings", "meeting summaries", "extract from meetings", "meeting insights".

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

小红书 AI 自媒体博主 (小红书 AI 自媒体博主 (从业者视角) — 在小红书做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具测评 / AI 绘画 / AI 教程与 prompt / AI 副业变现 / AI 资讯解读 / AI 效率，按小红书用户(偏年轻女性 + 泛知识)重构选题; (b) 文案与内容结构(核心) — 封面(第一眼/大字报/对比图)、标题(数字/痛点/好奇缺口/关键词前置)、正文(钩子开头/分点/口语化/emoji/利他价值)、标签与 SEO 关键词、CTA 与互动引导、人设 voice; (c) 内容制作工作流 — 选题(对标爆款/找选题)→标题封面→脚本或正文→制作(图文/口播/录屏/数字人)→标签发布→数据复盘迭代; (d) AI 工具用于内容生产 — 文案(豆包/Kimi/DeepSeek/GPT)、生图(即梦/MJ/可图)、口播数字人、剪辑(剪映)、封面(Canva/创可贴)、选题与 SEO(新红/千瓜/灰豚); (e) 平台机制与起号 — 推荐算法(收藏率/互动率/完播/搜索)、薯条投放、违禁词/限流/避坑、起号与涨粉、垂直度; (f) 变现(次要) — 蒲公英广告 / 知识付费 / 引流私域 / AI 工具带货。学派分歧: 图文 vs 短视频、干货教程 vs 测评种草 vs 资讯搬运、真人出镜 vs 数字人/无人起号、原创 vs 搬运洗稿、AI 全自动批量 vs AI 辅助精做。不含: 通用小红书运营(已有 xiaohongshu-ops skill, 本 skill 聚焦 AI 赛道 + 文案/内容生产)、电商带货全流程、其他平台、AI 工具本身的技术原理。) Master OS — automated mastery of 小红书 AI 自媒体博主 (从业者视角) — 在小红书做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具测评 / AI 绘画 / AI 教程与 prompt / AI 副业变现 / AI 资讯解读 / AI 效率，按小红书用户(偏年轻女性 + 泛知识)重构选题; (b) 文案与内容结构(核心) — 封面(第一眼/大字报/对比图)、标题(数字/痛点/好奇缺口/关键词前置)、正文(钩子开头/分点/口语化/emoji/利他价值)、标签与 SEO 关键词、CTA 与互动引导、人设 voice; (c) 内容制作工作流 — 选题(对标爆款/找选题)→标题封面→脚本或正文→制作(图文/口播/录屏/数字人)→标签发布→数据复盘迭代; (d) AI 工具用于内容生产 — 文案(豆包/Kimi/DeepSeek/GPT)、生图(即梦/MJ/可图)、口播数字人、剪辑(剪映)、封面(Canva/创可贴)、选题与 SEO(新红/千瓜/灰豚); (e) 平台机制与起号 — 推荐算法(收藏率/互动率/完播/搜索)、薯条投放、违禁词/限流/避坑、起号与涨粉、垂直度; (f) 变现(次要) — 蒲公英广告 / 知识付费 / 引流私域 / AI 工具带货。学派分歧: 图文 vs 短视频、干货教程 vs 测评种草 vs 资讯搬运、真人出镜 vs 数字人/无人起号、原创 vs 搬运洗稿、AI 全自动批量 vs AI 辅助精做。不含: 通用小红书运营(已有 xiaohongshu-ops skill, 本 skill 聚焦 AI 赛道 + 文案/内容生产)、电商带货全流程、其他平台、AI 工具本身的技术原理。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 小红书 AI 自媒体博主 (从业者视角) — 在小红书做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具测评 / AI 绘画 / AI 教程与 prompt / AI 副业变现 / AI 资讯解读 / AI 效率，按小红书用户(偏年轻女性 + 泛知识)重构选题; (b) 文案与内容结构(核心) — 封面(第一眼/大字报/对比图)、标题(数字/痛点/好奇缺口/关键词前置)、正文(钩子开头/分点/口语化/emoji/利他价值)、标签与 SEO 关键词、CTA 与互动引导、人设 voice; (c) 内容制作工作流 — 选题(对标爆款/找选题)→标题封面→脚本或正文→制作(图文/口播/录屏/数字人)→标签发布→数据复盘迭代; (d) AI 工具用于内容生产 — 文案(豆包/Kimi/DeepSeek/GPT)、生图(即梦/MJ/可图)、口播数字人、剪辑(剪映)、封面(Canva/创可贴)、选题与 SEO(新红/千瓜/灰豚); (e) 平台机制与起号 — 推荐算法(收藏率/互动率/完播/搜索)、薯条投放、违禁词/限流/避坑、起号与涨粉、垂直度; (f) 变现(次要) — 蒲公英广告 / 知识付费 / 引流私域 / AI 工具带货。学派分歧: 图文 vs 短视频、干货教程 vs 测评种草 vs 资讯搬运、真人出镜 vs 数字人/无人起号、原创 vs 搬运洗稿、AI 全自动批量 vs AI 辅助精做。不含: 通用小红书运营(已有 xiaohongshu-ops skill, 本 skill 聚焦 AI 赛道 + 文案/内容生产)、电商带货全流程、其他平台、AI 工具本身的技术原理。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「小红书 ai 博主」「小红书 ai 自媒体」「小红书 ai 赛道」「小红书爆款文案」「小红书 ai 教程」

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

小红书运营 (xiaohongshu operations) Master OS — automated mastery of xiaohongshu operations: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on xiaohongshu operations problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「小红书」「种草」「薯条」「信息流」「笔记」

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

Query TikTok global e-commerce market top-selling product rankings via FastMoss data, supporting daily/weekly/monthly dimensions and category-level analysis. Trigger when users mention TikTok bestseller chart, TikTok hot product ranking, TikTok sales ranking, TikTok GMV ranking, TikTok category bestsellers, TikTok weekly product report, TikTok top-selling rankings, TikTok bestseller charts, TikTok GMV ranking, TikTok category hot sellers, TikTok weekly product report, FastMoss. Even if the user does not explicitly mention "FastMoss", trigger this skill whenever their need involves viewing TikTok platform bestseller rankings or sales rankings by time dimension.

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

Retrieves patent abstract images (drawings) from the Nexscope (Nexscope) patent database by patent ID or publication number. Trigger when the user mentions patent abstract drawings, patent diagrams, patent figures, patent images, abstract drawing retrieval, patent image lookup, patent abstract images, patent drawings, patent illustrations, Nexscope, abstract image lookup. Also trigger when the user needs to view the drawings or figures in patent documents, even without explicitly mentioning Nexscope.

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

Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"

Expert knowledge of Behandlingsresultat (treatment result) domain in melosys-api. Use when: (1) Understanding result types and their meaning (FASTSATT_LOVVALGSLAND, MEDLEM_I_FOLKETRYGDEN, etc.), (2) Working with periods - Lovvalgsperiode, Medlemskapsperiode, Anmodningsperiode, Utpekingsperiode, (3) Debugging vedtak/decision metadata, criteria evaluation, or social insurance charges, (4) Understanding EU/EEA coordination logic and Article 16 exception handling, (5) Working with trygdeavgift (social insurance charge) calculations.

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

Manage project settings in sdd/sdd-settings.yaml including component settings that drive scaffolding.

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

Expert PE review of a submittal (shop drawings, product data, samples, equipment brochures) against specs, drawings, code questions and trade coordination. Produces findings with both sources, trade routing and a completeness gate. Triggers: 'review submittal', 'review shop drawings'.

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

小红书 / Xiaohongshu / RedNote AI Agent Skill。用 Python Playwright 搜索和读取内容、管理登录会话、发布图文/视频/长文、评论、点赞和收藏；默认输出 JSON，任何写操作都必须先获得用户确认。用户提到 xiaohongshu、小红书、rednote、小红书搜索、发到小红书、小红书笔记分析、小红书运营或小红书自动化时触发。

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

Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

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

Eilrechtsschutz gegen drohende Abschiebung und Duldungsantrag – § 80 V VwGO (insb. § 36 III AsylG 1-Wochen-Frist), § 123 VwGO, Duldung § 60a AufenthG, krankheitsbedingte Verbote § 60 VII AufenthG mit qualifizierter ärztlicher Bescheinigung § 60a IIc, Familienschutz Art. 6 GG / Art. 8 EMRK, EGMR Rule 39 als ultima ratio. Use when ein BAMF-Bescheid mit Abschiebungsandrohung zugestellt ist, eine Abschiebung unmittelbar droht oder Duldungsgründe entstanden sind.

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

Create colorful infographic PNGs from a conversation, topic, file, skill, or workflow. Use when: インフォグラフィック, 図解, 挿絵, 章扉, X投稿用画像, OGP, HTML→PNG, visualize session, poster image. Produces 2-3 self-contained HTML patterns, renders static PNGs, and verifies every image visually before reporting. Not for animated GIFs, architecture/sequence/flow diagrams (editable .drawio or interactive HTML), or HTML slide decks.

"Optimize multilingual product listings for international e-commerce including SEO localization, machine translation workflows, and cultural adaptation. Use this skill when the user needs to create product listings in multiple languages, optimize for local search, or adapt marketing content for different markets — even if they say 'translate our listings', 'optimize for local SEO', 'adapt for the Japanese market', or 'our translated listings don't convert'.".

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

"Summarize and analyze earnings calls (法說會) including financial highlights, management commentary, guidance, and analyst Q&A key takeaways. Use this skill when the user needs to digest an earnings call transcript, extract key financial data and forward guidance, compare actual results vs consensus estimates, or prepare for an investor meeting — even if they say 'summarize this earnings call', 'what did management say about next quarter', 'did they beat estimates', or 'key takeaways from the 法說會'.".

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

Use for Interpreter app settings and account usage. Prefer the direct workstation tools for reading settings, changing settings, and checking remaining Interpreter balance; use the Interpreter CLI only as a fallback.

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

Recovers obfuscated strings and resolves dynamically loaded APIs in malware: reversing XOR/stack-string/encoding schemes and mapping API-hash lookups back to function names. Activates for requests to deobfuscate strings, decode stack strings, or resolve API hashing in a binary.

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

Use when preparing for a Salesforce seasonal release — triaging release notes, reviewing Release Updates, opting into Sandbox Preview, and communicating change impact to stakeholders. Triggers: 'upcoming Salesforce release', 'release notes triage', 'Release Updates', 'sandbox preview opt-in', 'release readiness checklist', 'production upgrade date', 'feature impact', 'critical update', 'roll out the Spring release safely', 'is our org ready for the Spring release', 'release update settings metadata', 'FlowSettings release update field', 'release run sheet', 'preview sandbox refresh freeze', 'settings deploy flipped a release update'. Also covers: which Release Updates are deployable as Settings metadata, the release run sheet artefact, and the preview opt-in refresh-date rule. NOT for planning your own release train — use devops/release-management. NOT for user training and go-live comms — use admin/change-management-and-training.

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