653건 · 관련도순
Use after substantial web projects or repeated design defects to convert evidence into reusable skill improvements through root-cause analysis, regression scenarios, and controlled proposals without silently changing the core OS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open-format data ingestion for NV oOS Pro toolkits — the reusable pattern behind the F&B data-ingestion track (Proposal 078). Covers structural (header) matching over filename mapping, the configurable table_map + header-matcher + name-guess resolution order and the slug-first regression, the multi-format loader (CSV/TSV/JSON/JSONL/XLSX/ODS/PDF/photo), the Observation + terminology-map layer (vitals/FHIR analogue) with raw preservation, dedupe/retention/out-of-band banding, complete-by-default/resumable (offset) imports, and the read-only ingest-review dashboard anatomy (edit_posts review vs manage_options write, dry-run-first). Use when adding or extending data ingestion to a toolkit, ingesting heterogeneous owner files, wiring XLSX/PDF/photo imports, building an ingest/review dashboard, or debugging partial/truncated imports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operational guide for the NV oOS Model Foundry (Proposal 067) — the cluster fine-tuning flywheel. Phase 1 shipped: the Corpus Foundry (Pro addon, addons/pro/includes/model-foundry/) — consent-gated, deduplicated, PII-scrubbed corpus exporters (trajectory_v1, preference_v1, docs_v1) with deterministic holdout splits and R12 provenance manifests. Covers the governance contract, row schemas, output layout, filter seams, the registration pattern for foundry tool slices, how to add a new exporter, and the test/validation gates. Use when extending the Corpus Foundry, debugging corpus exports, wiring a new data source, or continuing Phases 2–6 (train-worker, registry/serving, eval gate, fleet sharing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate professional documents — PDF, Word (.docx), Excel (.xlsx), and invoices — from natural language descriptions or structured data. Covers AI-powered and simple document creation, HTML-to-PDF conversion, PDF extraction/OCR, merging, watermarking, and data export. Use when you need to create campaign decks, reports, proposals, invoices, spreadsheets, or any shareable document — especially for Step 7 monthly presentations, campaign briefs, and analytics reports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate or audit an `/llms.txt` file at the site root that makes the site legible to LLMs and AI answer engines at inference time, following the llms.txt proposal (Jeremy Howard, 2024). Use this skill whenever the user asks to "build llms.txt", "create llms.txt", "generate llms.txt", "audit llms.txt", "make my site LLM-friendly", "expose the site to AI assistants", "let ChatGPT / Claude / Perplexity cite my site", "add an AI assistants index", or asks about `.md` companion pages for LLM consumption. Output is a valid `llms.txt` file (or an audit) plus optional `.md` companion page generation for top pages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "run my launch day", "build a launch day runbook / war room", or "decide CONTINUE or ROLLBACK after the push"; produces a pre-conditions gate check (launch-readiness-auditor SHIP verdict + the authoritative date in launch-registry — missing either stops the skill), a dated hour-blocked runbook with owners (morning irreversible pushes, daytime monitoring loop, evening consolidation), a forced observation-window verdict after every irreversible action against pre-declared kill criteria, a P0-P3 incident ladder with rollback playbooks, and T-0 status lines for the registry proposal protocol. Not for channel submission content and platform rules — use community-launch-runner; not for media replies — use press-media-relations. 发布日runbook/作战室/观察窗/回滚裁决/发布日指挥
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "build our social crisis protocol", "mentions are exploding — what do we do first", or "when do we pause the posting queue"; produces a 1-5 severity ladder with tunable Estimated trigger thresholds (mention-velocity multiples vs the 7-day listening baseline, sentiment flip, journalist/regulator contact, employee-conduct class), the first-mechanical-action rule — pause ALL scheduled posts AND paid amplification, with dated state markers dropped to the channels proposal protocol and reconciled post-incident — a pre-approved holding-statement library with committed update cadences, when-NOT-to-post rules, a spokesperson/approval matrix, and a post-crisis retro template; re-runs the social-quality-auditor pre-publish gate before un-pausing the queue. Not for email deliverability incidents (blocklist, spam-rate spikes) — use deliverability-qa; inside a launch window launch-day-conductor owns incident handling. 社媒危机预案/暂停队列/声明库/发言人矩阵
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft cold emails, follow-ups, and proposal templates. Creates pricing pages, case studies, and sales scripts. Use PROACTIVELY for sales outreach or lead nurturing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create sales collateral such as decks, one-pagers, objection docs, demo scripts, playbooks, and proposal templates. Use when a sales team needs assets that help reps move deals forward and close.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create structured docs from scratch — PRDs, technical specs, design docs, decision records, knowledge bases. Use when drafting documentation, writing proposals, defining requirements, or planning features.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed plans, session IDs, transcripts, plan documents, PR descriptions, or pasted strategies; or when the user wants one recommended execution plan after agents review each other's proposals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stress-tests ideas by surfacing assumptions, counterarguments, and confidence gaps. Use when evaluating claims, proposals, plans, or decisions that need rigorous intellectual scrutiny.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: reviewing or producing any external-facing prose — ADRs, proposals, GitHub comments, Telegram messages, cover letters, client drafts, or planner-mode wording. Removes AI-tell patterns and raises writing quality before output leaves the team.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writing skill for freelancers and independent consultants. Covers project proposals, bids, client emails, and scope summaries. Leads with the client's problem, not the consultant's background.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when: planner mode, planning mode, proposal, scope definition, estimate, timeline, how hard, feasibility, effort, how long, how big, client message, external communication, pricing, delivery confidence, commercial risk, or project delivery planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants all 16 personality types (16-minds plugin) to vote on a proposal — yes/no/abstain — to see stakeholder distribution, detect hidden objections, or simulate organizational consensus. Triggers on Japanese phrases like 「全人格で投票」「16人格に賛否を聞いて」「ステークホルダーシミュ」「これ通せそう？」, English equivalents like "vote with all 16 minds" / "stakeholder simulation", or `--vote` flag on 16-minds commands. Different from /minds (which is for opinion divergence) — this is for binary judgment aggregation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user presents an idea/plan/proposal and wants a specific 16-minds (MBTI) personality to ask probing questions back — instead of giving an answer. Triggers on Japanese phrases like 「ENTPでツッコんで」「INFJに問い詰めて」「ENTJ視点で質問して」「このアイデア叩いて」, English equivalents like "as ENTP, question this" / "INFJ would ask what?", or 16-minds commands with a `--ask` flag. AIに「答えさせる」のではなく「問わせる」ためのSkill。ユーザーが思考を整理したい時に使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and operate a WeChat editorial content library in Busabase. Use when a team wants reusable source material, linked article drafts, an editorial kanban board, a publishing calendar, or a source-check and review queue. Keeps source documents and article scheduling in two linked Bases; does not publish to WeChat or approve an agent's own proposals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
4 business growth agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Customer success (health scoring, churn), sales engineer (RFP), revenue operations (pipeline, GTM), contract & proposal writer. Python tools (stdlib-only).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074/0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
クライアントの与件情報と打ち合わせメモから、意思決定に直結する調査プロジェクト提案書（スライド骨子/Markdown）を一発で作成するスキル。「提案書を作成して」「提案書を作って」「プロポーザルを作成して」などの依頼、または与件ファイル（例：与件.md）を指定して提案書作成を依頼された場合に使用する。単なる章立てではなく、調査の観点・仮説・参入障壁や供給構造・会議転用可能なアウトプットまで落として提案する。インプットや指示からデプスインタビューが必要と推測できる場合のみ、インタビュー前提の設計を含める。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reply to an applicant for an employer's Otameshi Tenshoku listing: match the application against the listed requirements item by item on what the applicant actually stated, list the questions still open, and draft an invitation, a request for clarification, a hold notice or a decline that sticks to the listed conditions, keeps other applicants and internal notes out, and presents any new work or dates as a proposal rather than an agreed term. Use when a hiring manager, recruiter or small-business owner has applications to answer, wants to know what to ask before inviting, or has to decline; do not use to judge an applicant's aptitude or predict hiring outcomes, to screen on personal attributes unrelated to the work, to design the work (trial-work-design) or the listing (trial-listing-draft), or to send the message or update applicant records on the user's behalf.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.