Plan a Chinese company's entry into an overseas market (出海): choose the market with evidence, then plan entity, payments, localisation, compliance, channels and team for the first twelve months. Use when asked 出海计划, 我们要进入东南亚 / 中东 / 欧洲 / 美国市场, how should a Chinese company expand overseas, or a go-global plan. Produces a market scorecard, a twelve-month entry plan by workstream, the compliance and data checklist for the chosen market, and the top risks with mitigations. Bilingual output on request.
日本語の概要は準備中です。原文の説明を表示しています。
mohitagw15856/pm-claude-skills☆ 1,4632026年10月15日 更新
Use when asked to walk me through an annual report, teach me to read this 10-K, explain a company's accounts to a beginner, or tutor me on the financial statements in an uploaded report. Walks a beginner up a fixed six-rung ladder — statement map, balance sheet line by line, operating profit to free cash flow, five sector-appropriate ratios with healthy ranges, the sceptical read, then a reusable checklist and a five-question quiz. Produces a page-referenced tutorial in which every figure cites the page it came from and anything missing is marked 'not disclosed in this report'. Educational, not financial advice.
日本語の概要は準備中です。原文の説明を表示しています。
mohitagw15856/pm-claude-skills☆ 1,4632026年10月15日 更新
Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label and evidence source with trust_summary rollup. Analyzes PDF schematics from dev boards, reference designs, eval kits, and datasheets. Supports KiCad 5–10. Use whenever the user mentions .kicad_sch, .kicad_pcb, .kicad_pro, PCB design review, schematic analysis, PDF schematics, reference designs, Gerber files, DRC/ERC, netlist issues, BOM extraction, signal tracing, power budget, DFM, or wants to understand, debug, compare, or review any hardware design. Also for "check my board", "review before fab", "what's wrong with my schematic", "is this ready to order", "check my power supply", "verify this circuit", OSHWA certification readiness, or any electronics/PCB design question.
日本語の概要は準備中です。原文の説明を表示しています。
aklofas/kicad-happy☆ 1,4042026年10月15日 更新
ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can we merge it" - in any language. You are the receiving party: treat the report as a claim, verify each part against machine state, name every gap between claimed and true. Verified-ready work merges in the same pass. End with what is left, one next step, and any reply another session needs, ready to paste.
日本語の概要は準備中です。原文の説明を表示しています。
kharmanskyi/open-steps☆ 1,3652026年10月6日 更新
ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report", "what's the status of this ticket" - in any language, and when a Stop hook asks for a session report. Produces a ten-line plain- language report: a lead, a checkmark table, and a verdict - fully done, anything needed from you, new debt, safe to close. Every "yes" names its proof; unverified says "not checked". Saves the report so the next session starts from it instead of re-exploring the repo.
日本語の概要は準備中です。原文の説明を表示しています。
kharmanskyi/open-steps☆ 1,3652026年10月6日 更新
ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is os-step-by-step. Reads the last report, local changes, open pull requests and always the backlog. First finishes what is finished: verified-ready pull requests merge in the same pass. Then sorts the rest into doable-alone and needs-you, ending with one recommended next task in plain words - what it closes or unblocks. Never invents tasks.
日本語の概要は準備中です。原文の説明を表示しています。
kharmanskyi/open-steps☆ 1,3652026年10月6日 更新
ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step", "walk me through it", "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do", in any language. Picking which task comes next is os-whats-next; this skill is for doing the thing in front of you. First earn the ask: try it yourself, find another route, shrink it to the part only they can do. Then one action per step, commands labelled by what they touch, no jargon. Commands are single lines that prompt for any value - typing hidden for secrets - and confirm in plain words. Afterwards verify their step.
日本語の概要は準備中です。原文の説明を表示しています。
kharmanskyi/open-steps☆ 1,3652026年10月6日 更新
ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words" - in any language. ALWAYS invoke it too when the user asks for your view on a technical choice: whether it is worth doing, more than the problem needs, or replaceable by something simpler, and which option you would take. Invoke it even when the code makes the answer look obvious: the checks are what make the answer more than a guess. Rewrites the question in plain words and always ends with one marked recommendation. A structural choice first passes six checks, shown as a table: effort now, simpler substitute, extra work later, lock-in, over-engineering, easy to undo. Doing nothing is always weighed.
日本語の概要は準備中です。原文の説明を表示しています。
kharmanskyi/open-steps☆ 1,3652026年10月6日 更新
ALWAYS invoke this skill before anything hard to undo gets agreed to - a contract, a purchase, a migration, a launch, a price change, a reorganisation - and whenever the user asks "what could go wrong", "what are we missing", "poke holes in this", or for a premortem or a red team, in any language. Assumes the decision already failed and works backwards to find out why, in a fresh agent that had no hand in making it. Sweeps nine areas and shows what each produced, including the empty ones. Ends on one verdict: go ahead, go but fix these first, try it small first, think again, do not do this.
日本語の概要は準備中です。原文の説明を表示しています。
kharmanskyi/open-steps☆ 1,3652026年10月6日 更新
Use this skill any time a .docx file is involved -- as input, output, or both. This includes: creating Word documents, reports, letters, memos, or proposals; reading, parsing, or extracting text from any .docx file; editing, modifying, or updating existing documents; working with templates, tracked changes, comments, headers/footers, or tables of contents. Trigger whenever the user mentions 'Word doc', 'document', 'report', 'letter', 'memo', or references a .docx filename.
日本語の概要は準備中です。原文の説明を表示しています。
Team-Commonly/commonly☆ 1,3632026年10月15日 更新
Use this skill any time a .pptx file is involved -- as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions 'deck', 'slides', 'presentation', 'pitch', or references a .pptx filename.
日本語の概要は準備中です。原文の説明を表示しています。
Team-Commonly/commonly☆ 1,3632026年10月15日 更新
Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or templates; importing CSV/TSV data into Excel format. Trigger whenever the user mentions 'spreadsheet', 'workbook', 'Excel', 'financial model', 'tracker', 'dashboard', or references a .xlsx/.csv filename.
日本語の概要は準備中です。原文の説明を表示しています。
Team-Commonly/commonly☆ 1,3632026年10月15日 更新
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly_* MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and work the task board. Load it the moment you see any commonly_* tool available.
日本語の概要は準備中です。原文の説明を表示しています。
Team-Commonly/commonly☆ 1,3632026年10月15日 更新
Refactor cleanly instead of layering sediment. Use for rename requests, stale or misleading names, legacy leftovers, changed scope, or when a change reveals duplicated concepts, local adapters, obsolete owners, redundant inputs or guards, compatibility wrappers, parallel abstractions, an over-large module that has accreted many responsibilities, or "just tack this on" pressure in any code area.
日本語の概要は準備中です。原文の説明を表示しています。
dzhng/skills☆ 1,3402026年10月15日 更新
Watches a company or topic on podcasts and YouTube: what was said lately (shows, counts, momentum, quotes), then an Arcmira monitor to keep following it.
日本語の概要は準備中です。原文の説明を表示しています。
hashgraph-online/awesome-codex-plugins☆ 1,3262026年10月15日 更新
Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label and evidence source with trust_summary rollup. Analyzes PDF schematics from dev boards, reference designs, eval kits, and datasheets. Supports KiCad 5–10. Use whenever the user mentions .kicad_sch, .kicad_pcb, .kicad_pro, PCB design review, schematic analysis, PDF schematics, reference designs, Gerber files, DRC/ERC, netlist issues, BOM extraction, signal tracing, power budget, DFM, or wants to understand, debug, compare, or review any hardware design. Also for "check my board", "review before fab", "what's wrong with my schematic", "is this ready to order", "check my power supply", "verify this circuit", OSHWA certification readiness, or any electronics/PCB design question.
日本語の概要は準備中です。原文の説明を表示しています。
hashgraph-online/awesome-codex-plugins☆ 1,3262026年10月15日 更新
INVOKE FIRST for any LangChain / LangGraph / Deep Agents agent building project before consulting other skills or writing any agent code. Required starting point for up to date info on framework selection (LangChain vs LangGraph vs Deep Agents vs hybrid composition), agent patterns, install, environment setup, and which skill to load next.
日本語の概要は準備中です。原文の説明を表示しています。
langchain-ai/langchain-skills☆ 1,2922026年10月9日 更新
Deterministic pre-publish scan that refuses AI-slop tells in anything about to be written, published, or sent: files, artifacts, slide titles, table headers, diagram labels, chat messages, commit messages. Use before publishing or sending any deliverable, in CI, or wired as a Claude Code hook so the check runs without being remembered. The editorial counterpart is no-ai-slop, which rewrites; this one blocks.
日本語の概要は準備中です。原文の説明を表示しています。
huytieu/COG-second-brain☆ 1,2832026年10月2日 更新
Measure your own writing corpus for the words and sentence shapes you over-use, so an agent writing in your voice stops amplifying your tics into a style. Produces a counted baseline file and checks any new draft against it. Use when an agent's drafts start sounding like a caricature of you, before publishing anything written in your voice, or every ten new pieces to re-measure.
日本語の概要は準備中です。原文の説明を表示しています。
huytieu/COG-second-brain☆ 1,2832026年10月2日 更新
Use when the theoretical puzzle is the bottleneck for an Academy of Management Review (AMR) manuscript — deciding whether an idea is theory-worthy and AMR-fit before any theorizing begins. Frames the puzzle; it does NOT build constructs (that is amr-theory-development) or design any empirical study (AMR has none).
日本語の概要は準備中です。原文の説明を表示しています。
brycewang-stanford/Awesome-Journal-Skills☆ 1,2602026年9月27日 更新
Comprehensive SEO footprint analysis. Catalogs all content, pulls real SEO metrics (via Apify Semrush/Ahrefs scrapers or free web search probes), runs competitor analysis, builds topic/keyword and content-type gap matrices, and produces a prioritized recommendations report. The complete SEO audit for any company.
日本語の概要は準備中です。原文の説明を表示しています。
gooseworks-ai/goose-skills☆ 1,2522026年10月16日 更新
Pre-sales-call intelligence composite. Deep dives on the person AND their company before a sales call, then maps findings to your product to generate talking points, objection prep, and a call strategy. Goes beyond generic attendee research — this is sales-specific intelligence that helps SDRs, AEs, and founders walk into calls with a plan. Tool-agnostic — works with any CRM, research source, and calendar.
日本語の概要は準備中です。原文の説明を表示しています。
gooseworks-ai/goose-skills☆ 1,2522026年10月16日 更新
Pipeline analysis composite. Pulls deal/meeting data from any CRM or tracking system, analyzes the pipeline over a user-defined period (weekly, fortnightly, monthly, quarterly), and produces both an executive summary and a detailed diagnostic report. Covers volume, qualification rates, source effectiveness, stage velocity, stuck deals, and actionable recommendations. Tool-agnostic — works with any CRM (Salesforce, HubSpot, Pipedrive, Close, Supabase, CSV).
日本語の概要は準備中です。原文の説明を表示しています。
gooseworks-ai/goose-skills☆ 1,2522026年10月16日 更新
Discover all customers of a given company by scanning websites, case studies, review sites, press, social media, job postings, and more. Use when you need competitive intelligence on who a company sells to.
日本語の概要は準備中です。原文の説明を表示しています。
gooseworks-ai/goose-skills☆ 1,2522026年10月16日 更新