「oss」の検索結果

口腔种植 (含 单牙/多牙缺失种植 / 全口 All-on-X / 即刻种植 即刻负重 / 上颌窦提升 / 牙槽嵴骨增量 GBR / 软组织移植 / 数字化种植 (CBCT 设计 + 口扫 + 导板 + CAD-CAM 上部) / 种植体周炎防治 / 种植修复 (基台 + 冠 + 杆卡 + 覆盖义齿) — 不含 普通牙体牙髓 / 正畸 / 儿牙 / 口腔颌面外科肿瘤 / 隐形矫治商业) (implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business.) Master OS — automated mastery of implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business.: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on implant dentistry — surgical placement and prosthetic restoration of osseointegrated dental implants; covers diagnosis & treatment planning, site preparation (bone augmentation, sinus elevation, soft-tissue grafting), implant placement (delayed / immediate / immediate-loading), provisionalization and final restoration (cement / screw retained, custom abutments, full-arch), digital workflow (CBCT planning, intra-oral scanning, guided surgery, CAD-CAM milled prosthetics), and long-term maintenance including peri-implantitis prevention and treatment; NOT general restorative dentistry, NOT orthodontics, NOT pediatric dentistry, NOT maxillofacial oncology / trauma reconstruction, NOT clear-aligner business. problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「种植牙」「种植」「口腔种植」「牙种植」「implant」

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

GitHub 解封 — 账号封禁/限制/恢复的领域操作系统。覆盖：(a) GitHub 官方政策体系 (TOS / 可接受使用政策 / Trust & Safety 执行模式 / 公开申诉路径 / 受制裁地区解读)；(b) 封号原因诊断学 (spam / abuse / 制裁误标 / 2FA 丢失 / ToS 违规 / 账号劫持误判 / ban evasion 等子类型 + 症状→原因映射 + 自我分诊压测)；(c) 申诉实操 craft (写一封能让 T&S 快速判误伤的英文申诉信 + 升级阶梯 + 法务介入边界 + Don'ts)；(d) 制裁与合规硬边界 (OFAC SDN 名单 / 哪些国家或地区真不可达 / VPN 误判路径 / 中国大陆不是美国制裁地区的反复重申)；(e) 中国大陆开发者特别处境 (sanctioned region 误标 + SMS 验证不支持 +86/+852 + Gitee/GitLab/Codeberg/JihuLab 备用迁移 + 私有自托管 Gitea/Forgejo)；(f) 真实案例库 (~30+ 公开案例分类拆解：误伤 / 真违规 / 制裁误标三类各自赔率与申诉成功路径)。伦理锚绝不软化：不教 ban evasion / 不教撒谎式申诉 / 真违规承认改进 / 丢 2FA 无恢复因子则诚实告知 / 中国制裁误标靠申诉不靠换 VPN / 申诉 6 个月窗口必算清 / 约 3% (业内估) 真违规恢复 vs 约 79% (业内估) 误伤申诉成功率分层标。 (GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: false-positive / genuine violation / sanctions mis-flag, each with win-rate and appeal success path). Ethical anchors absolutely not softened: do NOT teach ban evasion (creating new accounts turns a temp ban into a permanent one — the single biggest mistake); do NOT teach social engineering or lying in appeals (misuse + actually confirms violation); genuine violations: admit + improve beats denial; lost 2FA + no recovery factor → do not pretend recovery is possible; China sanctioned-region mis-flag → fix via appeal, not repeated VPN switching; appeal form 6-month window must be counted carefully; historical 约 3% (业内估) genuine-violation recovery vs 约 79% (业内估) false-positive appeal success rate stratification must be honestly labeled. Anti-samples (explicitly describe harm, never endorse): developer permabanned for ban evasion / open-source team org-banned for personal attacks in public issues / cases where repeated VPN switching escalated risk-control severity.) Master OS — automated mastery of GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: fa

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

Cross-chain & L2 Architect: Chain selection, rollups, bridges and cross-chain messaging with their trust assumptions.

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

Map curriculum connections across multiple subjects for a real-world problem or authentic context. Use when planning cross-curricular projects or connecting content to real issues.

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

Check an educational practice or task for cultural bias, WEIRD assumptions, and cross-cultural validity. Use when adapting resources for diverse contexts or questioning universal claims.

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

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.

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

Search and filter TikTok global e-commerce products based on FastMoss data, supporting keyword search, multi-dimensional filtering (category, shop type, commission rate, sales, creator count, etc.) and sorting. Trigger when users mention TikTok product selection, TikTok product search, TikTok product data, TikTok creator sales, TikTok commission rate, TikTok bestseller tracking, TikTok GMV analysis, TikTok product search, TikTok product research, TikTok creator sales, TikTok commission rate, TikTok GMV analysis, FastMoss. Even if the user does not explicitly mention "FastMoss", trigger this skill whenever their need involves searching product data or analyzing product performance on TikTok.

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

Query patent family information from Nexscope (Nexscope) by patent ID or publication number. Triggered when users mention patent family, patent family search, simple family, INPADOC family, Nexscope family, family patent lookup, patent equivalents, family members, cross-border related patent lookup, patent family, family patents, patent equivalents, cross-border patents, Nexscope, or INPADOC family. Even if the user does not explicitly say "patent family," this skill should be triggered whenever their need involves querying family members, equivalent patents, or related cross-border applications for one or more patents.

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

Use Nexscope data to search and filter Amazon products, supporting multi-dimensional criteria including price, monthly sales, BSR ranking, gross margin, ratings, fulfillment method, badges, seller origin, and more across multiple Amazon marketplaces. Trigger when the user mentions Amazon product selection research, product filtering, sales filtering, product discovery, BSR analysis, niche product discovery, competitor analysis, market opportunity assessment, product-level market size estimation, gross margin screening, Nexscope product selection, Amazon product selection, sales filtering, BSR analysis, profit screening, market analysis, product selection tool. Even if the user does not explicitly mention "Nexscope", if their need involves filtering and analyzing Amazon product-level data for product selection, this skill should also be triggered.

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

🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles. **Defaults to dev tools / OSS / B2B SaaS; for 2C products (education, apps, games) the launch channels & metrics differ — see gingiris-seo-geo/references/2c-adaptation.md.** 🇨🇳 AI 产品 / SaaS 企业出海完整 SOP — 从竞品调研到 Launch 到商业化的全流程操作手册。覆盖 Phase 0-5（市场验证、定位、前100用户、用户访谈、Beta转增长）+ 开源发布、Product Hunt、Reddit、SEO/GEO、转化与组织原则。**默认面向开发者工具/开源/B2B SaaS；2C 产品（教育/应用/游戏）的启动渠道与指标不同，见 gingiris-seo-geo/references/2c-adaptation.md。** 🇯🇵 AI製品/SaaS海外展開フルサイクルSOP — 競合調査からローンチ、マネタイズまで。Phase 0-5（市場検証、ポジショニング、最初の100ユーザー、ユーザーインタビュー、ベータから成長）＋オープンソース、Product Hunt、Reddit、SEO/GEO、コンバージョン、組織原則。 🇰🇷 AI 제품/SaaS 글로벌 진출 완전 SOP — 경쟁사 조사부터 런칭, 수익화까지 전 주기 플레이북. Phase 0-5(시장 검증, 포지셔닝, 첫 100명 사용자, 사용자 인터뷰, 베타→성장) + 오픈소스 런칭, Product Hunt, Reddit, SEO/GEO, 전환, 조직 원칙. Triggers: "go global" | "出海" | "overseas expansion" | "GTM" | "cold start" | "launch strategy" | "international expansion" | "海外增长" | "出海SOP" | "product launch overseas" | "海外进出" | "グローバル展開" | "글로벌 진출" | "go-to-market" | "出海打法"

🇺🇸 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" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"

Design loss control programs. TRIGGERS - Use when user needs help with insurance-loss-control related tasks.

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

Quantify cyber risk using FAIR methodology with Monte Carlo simulation, assess control effectiveness against NIST CSF/CIS/ISO 27001 frameworks, evaluate risk appetite alignment, and analyze cyber insurance coverage adequacy. Covers threat landscape mapping, asset valuation, loss event frequency and magnitude estimation, annualized loss expectancy calculation, control gap analysis with ROI ranking, residual risk assessment, and insurance policy gap modeling at 90th/95th/99th percentile loss scenarios. Use when building risk registers, preparing board-level risk dashboards, evaluating security investment priorities, assessing cyber insurance coverage, or auditing any organization's risk quantification maturity per NIST RMF, ISO 27005, or FAIR standards.

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

Cyber Risk Quantification engineer for CyberRadar. Implements FAIR (Factor Analysis of Information Risk) methodology, Monte Carlo simulation for loss distribution modeling, financial impact quantification in multi-currency (SAR, USD, EUR, GBP), loss exceedance curves, risk treatment ROI calculation, insurance premium optimization, and board-ready financial risk reporting. Transforms qualitative risk assessments into monetary terms for executive decision-making. Triggers on: CRQ, FAIR, Monte Carlo, financial impact, loss modeling, risk quantification, cyber insurance, risk treatment ROI, financial risk.

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

Design cross-selling strategies for insurance products. TRIGGERS - Use when user needs help with cross-selling-insurance related tasks.

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

Evaluates loss reserve adequacy with development triangle analysis and actuarial methods. Use when analyzing reserves, interpreting loss triangles, or assessing reserve adequacy.

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

Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards. USE THIS SKILL WHEN: - You need to review or audit actuarial models (reserving, pricing, capital) - Someone asks about loss triangle analysis or reserve adequacy - You are evaluating IBNR calculations, chain ladder methods, or Bornhuetter-Ferguson - A project involves insurance pricing, GLM rating models, or ratemaking - You need to assess Solvency II SCR calculations or RBC compliance - Someone mentions actuarial opinions, ASOP compliance, or SOA standards - You are reviewing stochastic models, ESG configurations, or DFA frameworks - A codebase uses actuarial libraries (chainladder, lifetables, ChainLadder R package) TRIGGER PHRASES: "actuarial", "loss reserving", "IBNR", "chain ladder", "premium pricing", "mortality table", "Solvency II", "capital adequacy", "ratemaking", "GLM pricing", "risk-based capital", "reserve analysis", "actuarial opinion"

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

Pragmatics and communicative competence across languages -- speech acts (Austin/Searle), Grice's conversational maxims and implicature, politeness theory (Brown & Levinson), face-threatening acts, discourse structure, turn-taking, repair strategies, register and formality, cross-cultural communication, communicative strategies (circumlocution, approximation, appeal for assistance), and the gap between grammatical competence and communicative performance. Use when teaching communication skills, analyzing cross-cultural misunderstandings, building conversational fluency, or understanding why grammatically correct sentences can be pragmatically inappropriate.

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

Grammar and syntactic structures across human languages -- word order typology (SVO, SOV, VSO, VOS, OVS, OSV), morphological systems (isolating, agglutinative, fusional, polysynthetic), agreement patterns (gender, number, case, person), phrase structure, clause embedding, and cross-linguistic universals. Covers constituent analysis, dependency vs. constituency grammars, grammatical relations (subject, object, oblique), ergativity vs. accusativity, tense-aspect-mood systems, and how grammar encodes meaning differently across language families. Use when analyzing sentence structure, comparing grammar systems, teaching grammatical concepts, or understanding why a learner makes transfer errors from their L1.

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

Cascade the same edit pattern across N files safely. Use when applying the same refactor to multiple files (e.g. swap import paths across 11 scripts, rename a symbol, migrate a call signature). Detects the common-shape-across-files situation and turns an N-file cascade into a planned audit → apply → verify workflow instead of N sequential manual edits.

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

Meta-mathematical connections, cross-domain synthesis, and the Complex Plane as a navigational tool. Classifies problems by quadrant (Abstract/Embodied x Logic/Creativity), routes them to relevant domains, and traces dependency chains. Use when classifying mathematical problems across domains, navigating the Complex Plane of Experience, finding cross-domain connections, or building multi-domain solution strategies.

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

Structured cross-review protocol between specialized agents. Ensures scope alignment, priority calibration, and domain-aware feedback. Use when one agent reviews another's work, during handoffs, or when validating cross-cutting concerns.

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

Submit a pull request following the repo's contribution guidelines. Reviews the diff, checks for common rejection reasons, and helps the user write their own PR description. The LLM reviews. the user writes. Use when implementation is complete and tests pass. Not for responding to review comments after the PR is open. Use oss-post-pr for that.

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

Contribute documentation improvements to an OSS repo. Identifies doc gaps, studies the docs system, and verifies accuracy against source code. Use when contributing documentation to an open source project, fixing outdated setup instructions, adding missing API docs, or improving README clarity. Not for writing docs for your own project — this is for contributing docs to someone else's repo.

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