「source」の検索結果

Plan, implement, or review source management work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests source management work.

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

Structure prediction using Boltz-1/Boltz-2, an open biomolecular structure predictor. Use this skill when: (1) Predicting protein complex structures, (2) Validating designed binders, (3) Need open-source alternative to AF2, (4) Predicting protein-ligand complexes, (5) Using local GPU resources. For QC thresholds, use protein-qc. For AlphaFold2 prediction, use alphafold. For Chai prediction, use chai.

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

Boltz-1 / Boltz-2 structure prediction for proteins, complexes, and ligand-aware validation. Use this skill when: (1) Predicting protein complex structures, (2) Validating designed binders, (3) Need open-source alternative to AF2, (4) Predicting protein-ligand complexes, (5) Using local GPU resources. For QC thresholds, use protein-design-qc. For AlphaFold2 prediction, use alphafold2-multimer. For Chai prediction, use chai1-structure-prediction.

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

This skill should be used when the user wants to query their Google NotebookLM notebooks for citation-backed, source-grounded answers, or manage notebooks, sources, and Studio content (audio, report, video, infographic, presentation, data table, flashcards, quiz, mind map). It drives the @roomi-fields/notebooklm-mcp engine — via the notebooklm MCP tools when they are available in the session, otherwise via its HTTP REST API — and covers Google login, citation formats, the daily-quota-aware batch/ingestion pattern, and source discovery.

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

Finds orphaned, idle, and underutilized cloud resources across AWS, GCP, or Azure accounts. Use when someone needs to audit cloud spending, find unused EBS volumes, stale snapshots, unattached IPs, idle load balancers, or oversized RDS instances. Trigger words: cloud waste, orphaned resources, unused volumes, cloud audit, infrastructure cleanup, cloud bill analysis.

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

Deploys and integrates Chatwoot, an open-source customer support platform with live chat and a shared multi-channel inbox. Use when a user asks to set up open-source customer support, add live chat without SaaS costs, build a multi-channel inbox, or deploy a free Intercom alternative.

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

Activepieces is an open-source workflow automation platform with a visual builder, 400+ integrations ("pieces"), code steps, branching, loops, and webhooks. Use when a user asks to self-host a Zapier or n8n alternative, automate workflows with a no-code builder, build a custom integration piece, or set up open-source business automation.

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

Building production-ready Model Context Protocol servers that expose tools, resources, and prompts to AI assistantsUse when "mcp server, model context protocol, mcp tool, mcp resource, claude integration, ai tool integration, mcp, model-context-protocol, anthropic, claude, ai-integration, tools, resources, prompts" mentioned.

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

Expert Godot 4 game developer specializing in GDScript, the node/scene system, signals, resources, and engine-native patterns. Provides deep knowledge of Godot's unique architecture, performance optimization, and best practices for building games from simple prototypes to production-ready releases. Use when "godot, gdscript, godot 4, godot engine, build a game with godot, godot scene, godot node, godot signal, godot resource, godot tilemap, godot physics, godot animation, godot ui, godot multiplayer, godot, gdscript, game-engine, game-development, 2d-games, 3d-games, open-source" mentioned.

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

游戏设计 (Game Design) — 设计游戏的规则 / 系统 / 机制 / 体验 的从业者认知操作系统 (以电子游戏为主, 含桌游 / 卡牌 / 棋盘游戏): 决定「玩家做什么、为什么有意义、每一刻的体验如何」的学科 —— 区别于游戏程序 (引擎 / 代码)、游戏美术 (视觉 / 音频)、游戏制作 (排期 / 预算 / 团队)。覆盖 (a) 核心设计理论与框架 (MDA 机制-动态-美学 Hunicke/LeBlanc/Zubek + Schell 的「透镜」+ Koster「乐趣即学习」理论 + Sid Meier「一连串有趣的决策」+ Salen & Zimmerman「有意义的游玩」/「二阶设计」/「魔法圈」+ Costikyan 论不确定性 + Suits/Huizinga 游戏哲学), (b) 系统与机制设计 (核心循环 + 游戏经济 sink/source/产出-消耗 + 正负反馈环 + 资源与成长系统 + 涌现 vs 脚本 Will Wright「可能性空间」+ Machinations 经济建模 Dormans + 支配 / 退化策略 + 正交设计 Garfield), (c) 关卡与遭遇设计 (灰盒 blockout + 节奏与张力 + 预告 telegraphing + 主线 vs 探索 + 环境叙事 + 锁钥 gating + 难度曲线), (d) 游戏手感与「juice」(Steve Swink《Game Feel》+ 即时响应 + 屏震 / 反馈 / 打磨 + 输入与镜头 + 「手感」是设计出来的不是附带的), (e) 玩家心理与 UX (Celia Hodent《The Gamer's Brain》+ 心流通道 挑战 vs 技能 Csikszentmihalyi/陈星汉 Jenova Chen + Bartle 玩家类型 + 动机与奖励节奏 + 新手引导 FTUE / 教学化 + 认知负荷 + 无障碍), (f) 平衡与调优 (Ian Schreiber《Game Balance》+ 对称 / 非对称 + 动态难度 DDA + 传递 / 非传递平衡 + nerf/buff + 消除支配策略 + 测试驱动调优), (g) 叙事与任务设计 (ludonarrative 失调 / 和谐 + 环境与系统叙事 + 分支 vs 线性 + Amy Hennig 角色驱动 + 任务结构), (h) 以玩家为中心的迭代流程 (Tracy Fullerton《Game Design Workshop》playcentric + 纸面原型 + 垂直切片 + 测试协议「看而不说 / 你不是你的玩家」+ 快速迭代 + game jam), (i) 类型与形态工艺 (roguelike/roguelite 与程序生成 Derek Yu + 平台跳跃 + RPG 系统 + 策略 4X + 解谜设计 Jonathan Blow + 多人 / PvP 平衡 + 桌游 / 卡牌设计 Reiner Knizia/Richard Garfield/Brenda Romero), (j) F2P / 长线运营 / 商业化设计 (核心 / 元 / 经济循环 + 抽卡 gacha / 开箱 loot box / 战令 battle pass 机制 + 留存 D1/D7/D30 + 转化 + 鲸鱼 + live ops 内容节奏 —— 并诚实处理掠夺式暗黑模式 / 强迫循环 / 剥削式商业化的伦理), (k) 设计师角色与工艺职业 (系统 / 关卡 / 叙事 / UX 设计师之分 + 通才 vs 专才 + 独立作者 vs 3A 团队 + 设计文档 + 传达设计意图 + GDC 工艺社区)。跨 3A / 独立 / 手游 F2P / 桌游。不含 游戏程序 / 引擎 (Unity/Unreal 编码 / 图形 / 网络同步) / 游戏美术 / 动画 / 音频 / 游戏制作 / 项目管理 / 排期 / QA / 游戏作为生意 / 发行 / 市场 / 电竞运营为终点 / 泛泛「我想做游戏」的 game-dev 教程 —— 本 skill 是「设计」学科: 规则 / 系统 / 机制 / 体验。 (Game Design — the cognitive operating system of practitioners who design the rules, systems, mechanics, and experiences of games (video games primarily, plus tabletop/board/card games): the discipline of deciding WHAT the player does, WHY it is meaningful, and HOW the moment-to-moment experience feels — distinct from game programming (builds the engine/code), game art (visuals/audio), and game production (schedule/budget/team). Covers (a) core design theory & frameworks (MDA Mechanics-Dynamics-Aesthetics Hunicke/LeBlanc/Zubek, Schell's Lenses, Koster's theory of fun = learning, Sid Meier 'a series of interesting decisions', Salen & Zimmerman 'meaningful play'/'second-order design'/'magic circle', Costikyan on uncertainty, Suits/Huizinga play philosophy), (b) systems & mechanics design (core loops, game economy sink/source/faucet-drain, feedback loops positive/negative, resource & progression systems, emergence vs scripting Will Wright 'possibility space', Machinations economy modeling Dormans, dominant/degenerate strategy, orthogonal design Garfield), (c) level & encounter design (blockout/greybox, pacing & tension, telegraphing, critical path vs exploration, environmental storytelling, gating & lock-and-key, difficulty curve), (d) game feel & juice (Steve Swink 'Game Feel', moment-to-moment responsiveness, screenshake/feedback/polish, input & camera, the 'feel' is designed not incidental), (e) player psychology & UX (Celia Hodent 'The Gamer's Brain', flow channel challenge-vs-skill Csikszentmihalyi/Jenova Chen, Bartle player types, motivation & reward schedules, onboarding/FTUE/tutorialization, cognitive load, accessibility), (f) balancing & tuning (Ian Schreiber 'Game Balance', symmetry/asymmetry, dynamic difficulty adjustment DDA, transitive/intransitive balance, nerf/buff, dominant strategy elimination, playtesting-driven tuning), (g) narrative & quest design (ludonarrative dissonance/harmony, environmental & systemic storytelling, branching vs linear, Amy Hennig character-driven, quest structure), (h) player-centric iterative process (Tracy Fullerton 'Game Design Workshop' playcentric design, paper prototyping, vertical slice, playtesting protocol 'watch don't talk / you are not your play

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

Prospects companies across developer-focused tech verticals for developer marketing agency outreach. Use this skill whenever a user provides a vertical (e.g. AI Agentic, IAC, DevTools, Observability, DevOps, FinOps, AI/SDLC, AI Orchestration, or any other tech vertical) and wants a list of prospect companies to target. Also trigger when the user says "prospect for", "find companies in", "give me leads for", "build a prospect list", or provides a vertical name alongside funding stage and headcount filters. Always use this skill — never attempt prospecting without following this structured workflow. The skill finds exact-fit companies only (never adjacent), maps a real outreach signal and email pain point for each, sources every data point with a URL, and outputs a unified nine-column table: Company, URL, LinkedIn, Headcount, Signal, Signal Sources, Geography, Pain Point, Pain Point Sources.

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

Suede AI MCP release QA, scoped to this pack's own server (mcp/suede-skills-mcp.mjs) and its catalog, install, and docs surface. Runs the full JSON-RPC lifecycle against a live server (initialize, notifications/initialized, ping, tools/list, tools/call, resources/list, resources/read, prompts/list, prompts/get), plus protocol negotiation, closed input and output schemas, tool annotations, structuredContent with text fallbacks, malformed-input probes, clean stdio, catalog-to-folder agreement, and install-path language. Use when the MCP server, mcp/catalog.json, a tool, resource, or prompt definition, or the MCP install docs change, or before publishing an MCP release. A check that did not run against the live server is a FAIL, not a skip. NOT FOR: a generic third-party MCP server, which this skill's hardcoded surface does not describe; fixing or testing the public install path itself (use suede-launch-packaging).

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

Deep research with web search, source verification, and fact-checking. Runs before humanize + kami in the document pipeline. Use when user asks to research a topic, verify facts, gather sources, or do deep web investigation. Covers source validation, citation, and evidence hierarchy.

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

Analyze WeChat Mini Program platform constraints and evidence layers for an idea or existing repository, including source configuration, build output, WeChat DevTools loading, device behavior, permissions, privacy declarations, cloud or backend linkage, upload, trial, review, and production status. Use when users ask about WeChat-specific configuration, project roots, compile paths, capability permissions, privacy compliance, official platform rules, upload or release readiness, or why source and platform behavior differ. Performs read-only evidence classification by default, verifies time-sensitive or high-risk claims against current official WeChat sources, redacts identifiers and secrets, and never upgrades one evidence layer into another.

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

You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the community & ambassador operations SOP with volunteer, paid tutorial creator and code-contributor tracks — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp programs. By @WeiYipei. 🇨🇳 你搞了个大使计划。来了3个申请。一个第二周就消失了。该降门槛？加福利？群发KOL？这份SOP给你从启动前置条件到招募到留存到治理的完整社区/大使运营方法论。基于 Notion（2000万用户，大使真实访谈）、AFFiNE（60K stars）、Asana、ClickUp 实战案例。 🇯🇵 アンバサダープログラムを立ち上げた。応募3件。1人は2週間で消えた。基準を下げる？特典を増やす？このSOPは、事前チェックリストから採用、段階管理、リテンション、ガバナンスまでの完全なコミュニティ＆アンバサダー運営フレームワークを提供します。Notion（2000万ユーザー）、AFFiNE（60K stars）の実例から構築。 🇰🇷 앰배서더 프로그램을 시작했습니다. 지원 3건. 하나는 2주 만에 사라졌습니다. 기준을 낮출까요? 이 SOP는 사전 체크리스트부터 모집, 단계별 관리, 리텐션, 거버넌스까지 완전한 커뮤니티 & 앰배서더 운영 프레임워크를 제공합니다. Notion(2000만 사용자), AFFiNE(60K stars) 실전 사례에서 구축. Triggers: "ambassador program" | "community building" | "community management" | "DevRel" | "developer relations" | "community growth" | "大使计划" | "社区运营" | "社区搭建" | "コミュニティ運営" | "アンバサダー" | "커뮤니티 운영" | "앰배서더" | "open source community" | "user retention"

You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the complete community & ambassador operations SOP — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp programs. By @WeiYipei. What's inside: • Pre-launch readiness checklist (6 conditions that must be true before starting) • 6-step community setup SOP (platform selection → rules → admin standards → monitoring → wiki → metrics) • Ambassador recruitment system (A+B qualification, application form design, scoring rubric) • 4-tier progression system (Bronze → Silver → Gold → Platinum with point thresholds) • 5-pillar incentive framework (Product quality → Beta access → Founder access → KOL path → Full engagement) • Churn early-warning system + retention playbook • Event operations SOP (6 event types × full lifecycle) • Health metrics dashboard (6 core KPIs + 5 ambassador-specific indicators) • Governance & risk control (behavior code, escalation matrix) • Real templates: recruitment post, welcome email, annual calendar 🇨🇳 你搞了个大使计划。来了3个申请。一个第二周就消失了。该降门槛？加福利？群发KOL？这份SOP给你从启动前置条件到招募到留存到治理的完整社区/大使运营方法论。基于 Notion（2000万用户，大使真实访谈）、AFFiNE（60K stars）、Asana、ClickUp 实战案例。 🇯🇵 アンバサダープログラムを立ち上げた。応募3件。1人は2週間で消えた。基準を下げる？特典を増やす？このSOPは、事前チェックリストから採用、段階管理、リテンション、ガバナンスまでの完全なコミュニティ＆アンバサダー運営フレームワークを提供します。Notion（2000万ユーザー）、AFFiNE（60K stars）の実例から構築。 🇰🇷 앰배서더 프로그램을 시작했습니다. 지원 3건. 하나는 2주 만에 사라졌습니다. 기준을 낮출까요? 이 SOP는 사전 체크리스트부터 모집, 단계별 관리, 리텐션, 거버넌스까지 완전한 커뮤니티 & 앰배서더 운영 프레임워크를 제공합니다. Notion(2000만 사용자), AFFiNE(60K stars) 실전 사례에서 구축. Triggers: "ambassador program" | "community building" | "community management" | "DevRel" | "developer relations" | "community growth" | "大使计划" | "社区运营" | "社区搭建" | "コミュニティ運営" | "アンバサダー" | "커뮤니티 운영" | "앰배서더" | "open source community" | "user retention"

Marketing playbook for open-source projects led by non-technical founders. Covers README optimization, community building, contributor attraction, and translating OSS traction into revenue. By @WeiYipei.

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

Verify claims, quotes, timelines, and findings against supplied source files and return a source map with verified, conflicting, not found, and manual-review statuses. Use when the user asks to fact-check a memo, audit, timeline, executive summary, research packet, or project brief against PDFs, XML, HTML, notes, screenshots, exported chat logs, or other supplied files before sending, publishing, or relying on the result.

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

Integrate multiple source findings into an attributed synthesis or comparison. Use for combine these summaries, synthesize results, merge findings or multi-source analysis. Preserve claim-level provenance, coverage, qualifiers, conflicts and uncertainty rather than repeatedly compressing narrative summaries.

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

Scaffolds or audits a research-project repository organized around its source library (original PDFs, tracked Markdown conversions, drop zone, bibliography, intake pipeline) plus the analysis, manuscript, and review folders the project type needs. Use when starting, structuring, or auditing a research repo or its sources folder. Single-PDF intake goes to process-source, replication packages to replication-package.

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

Audits a manuscript's citations for fabricated or nonexistent sources, DOIs that resolve to a different work, mismatches between in-text citations and the reference list, APA 7 or journal style, and whether each source supports the claim it is attached to. Checks entries against Crossref, OpenAlex, and DataCite and labels anything it could not verify NOT CHECKED. Use to check citations, references, a .bib file, or DOIs, or when a source may be AI-invented. Figures and tables go to figure-table-audit.

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

Fact-check manuscript claims against their cited sources in a per-source Markdown knowledge base. Use to audit claim support, overclaiming, direction, scope, and misattribution after source intake is complete.

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

Add new learning resources (books, articles, courses, papers) to the appropriate resources.md file. Use when user mentions adding, saving, or tracking learning materials.

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

Review touched Incan source for Python-quality readability, idiomatic Incan structure, dogfooding integrity, public API polish, and source-level anti-patterns. Use for `.incn` stdlib, examples, language-surface implementations, or when the user asks whether Incan code reads like well-written Python rather than Rust-shaped scaffolding.

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