4,164 件 ・ 関連度順
概要と使いどころ
ktx's knowledge base - wiki pages for durable, reusable business knowledge. Covers capture workflow for user preferences, metric definitions, organizational conventions, and cross-references between wiki pages and semantic-layer sources. Loaded by the post-turn memory-agent only. The research agent reads wiki via `wiki_read`/`wiki_search` but does not write it.
日本語の概要は準備中です。原文の説明を表示しています。
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or ChatGPT citation optimization of supplied writing; when they want an evidence-aware pre-publication audit; or when another Newsjack workflow needs a prose-level AI-discoverability pass. Do not use as a technical SEO audit, rank tracker, publishing system, or promise of rankings, mentions, citations, traffic, or coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Draft crisis holding statements, journalist Q&A posture, and what-not-to-say guidance from confirmed incident facts, with a hard legal-counsel gate. Builds each statement through proven crisis-comms frameworks (holding-statement anatomy, SCCT, CAP order, the legitimate non-answer, bridge/flag/block).
日本語の概要は準備中です。原文の説明を表示しています。
Software supply chain security reference for OpenSSF Scorecard, SLSA, Sigstore, SBOM, and posture/backlog taxonomies.
日本語の概要は準備中です。原文の説明を表示しています。
Jira issue workflows for search, issue updates, transitions, comments, field discovery, and interactive credential setup via the Jira REST API. Use when you need to configure Jira access, search with JQL, inspect an issue, create or update work items, move an issue between statuses, post comments, or discover required fields for issue creation.
日本語の概要は準備中です。原文の説明を表示しています。
Run /document `pr` | `changelog` | `release-note` | `postmortem` (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
日本語の概要は準備中です。原文の説明を表示しています。
Writes, tests, registers and debugs Claude Code hooks (PreToolUse, PostToolUse, SessionStart, Stop) that turn a rule the model keeps breaking into a hard gate. Use when the user wants to block or intercept a tool call, add a guard rail, fix a misfiring hook, or says 拦截 / 守卫 / 钩子 — including "make it stop doing X".
日本語の概要は準備中です。原文の説明を表示しています。
Consolidates redundant documentation while preserving all valuable content; keeps a doc set truthful after things change. Modes: (1) POST-CHANGE GOVERNANCE — when code, scripts, config, env vars, ports, paths, deployment, auth, tests, or a documented procedure changed; also "which docs are now wrong", "check docs for inconsistencies", "过时的命令/路径", "文档同步". Use it even when the user mentions only the change and never the docs — updating them is part of the change, not optional cleanup. (2) CONSOLIDATION — "clean up docs", "documentation bloat", "reduce documentation sprawl", "consolidate documentation", "too many doc files", "merge redundant docs", "merge these docs", "文档太多/太乱", multiple files covering the same topic, or documentation exceeding 500 lines across multiple files on similar topics. Finds stale copies of a fact changed in only one place, values that should never have been persisted (counts, totals, "N items", restated summaries), rival definitions that drift apart, and orphaned cross-references.
日本語の概要は準備中です。原文の説明を表示しています。
Two pipelines ending at a scanner-look PDF. (1) Phone photos of paper documents (contracts, stamped certificates, receipts, forms, handwritten notes) → clean scanner-quality PDF: perspective rectification + noteshrink whitening + A4 assembly + mandatory whole-document check. Trigger: "把照片 做成扫描件", "photos to scanned PDF", "make this look scanned", "手机拍的 文档转 PDF", "盖章文件扫描", replacing pages in an existing scanned PDF, any CamScanner-like request. (2) A digital document with no signature yet (rendered docx/PDF, confirmation form, contract draft) → make it look hand-signed and scanned: synthesize a handwriting-style signature, composite it onto the signature line, apply the same scan-look post-processing. Trigger: "帮我做个手写签名", "生成签名盖到这份文件上", "做成签过字的扫描件", "synthesize a signature", any request for a document that needs to look signed without a real photographed signature. Do NOT hand-roll levels/contrast enhancement for scan-look — tried and rejected twice; this skill's pipeline is the proven one.
日本語の概要は準備中です。原文の説明を表示しています。
Converts DOCX/PDF/PPTX and saved HTML/HTM to high-quality Markdown with automatic post-processing. Fixes pandoc grid tables, simple tables, image paths, CJK bold spacing, attribute noise, and code blocks; for PDFs also strips OCR garbage blocks, repeated headers/footers/watermarks, and absolute image paths from pymupdf4llm output. Benchmarked best-in-class (7.6/10) against Docling, MarkItDown, Pandoc raw, and Mammoth. Trigger on "convert document", "docx to markdown", "parse word", "doc to markdown", "解析word", "转换文档", "HTML to Markdown".
日本語の概要は準備中です。原文の説明を表示しています。
Routes docs: Word/PDF/PPTX/saved HTML→Markdown; MD/Word→PDF; create Word; PDF HTML/translate; Excel/xlsm/macOS; photo/signed scans; Mermaid; DOCX review; post-change docs. Reads one bundled Daymade specialist. New slide decks use deck-creator when installed; generic PDF reading/editing and spreadsheet analysis stay with their own Skills. Retired ppt-creator stays manual-only.
日本語の概要は準備中です。原文の説明を表示しています。
Bridges Claude Code and Codex sessions when native tools can't reach the target. Use for 跨产品通信 / 脚本回帖 / 送达排查: cross-product messages, hooks or scripts posting to a session, verifying delivery (Held messages included), shared-work ownership, or an inbound peer assertion. Not for same-product or parent/subagent messaging (use native tools), spawning agents, moving full history, or cross-machine pairing (deprecated).
日本語の概要は準備中です。原文の説明を表示しています。
Co-creates a personal investment-research LLM Wiki (Karpathy's pattern) by interviewing the user for THEIR OWN analysis framework, not a template — a living CLAUDE.md of pure markdown + wikilinks, no RAG in place of compilation. Use to build a compounding 投研第二大脑 / 投研知识库 / 个人投研 wiki, ingest research reports / earnings calls into an existing wiki, or run post-earnings prediction→fulfillment reviews.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when picking or diagnosing a training move (SFT, LoRA, DPO/KTO/ORPO, RFT, GRPO/PPO/RLOO, RLHF), or when the user mentions fine-tuning, post-training, training recipe, reward design, or weight updates. Decision tree by reward shape, smoke-run gate, three failure diagnostics, five false-progress patterns. Provider recipes and I/O contract in references/.
日本語の概要は準備中です。原文の説明を表示しています。
Define a creator's brand foundation — niche, audience, positioning, content pillars, voice/tone, and bio — so every post is consistent and on-brand. Use when asked to define a creator brand, find a niche, set content pillars, write a voice guide, craft a bio, or build a brand kit for a personal brand or channel. Produces a reusable one-page brand kit that other content skills can read so output sounds like you, every time.
日本語の概要は準備中です。原文の説明を表示しています。
Plan preparation for the Chinese postgraduate entrance examination (考研): choosing target schools and programmes with realistic odds, a phased study plan for the national subjects and the specialist papers, and preparation for the re-examination (复试) and adjustment (调剂). Use when asked 考研怎么规划, 帮我做考研复习计划, 择校择专业, 考研时间线, 复试怎么准备, 调剂, or plan my kaoyan. Produces a school-and-programme shortlist method with the data to collect, a month-by-month study plan by subject, weekly templates, the key-date checklist to confirm against official notices, and a 复试 and 调剂 preparation guide.
日本語の概要は準備中です。原文の説明を表示しています。
Write clear at-home care instructions for a pet owner after a veterinary visit, procedure, or hospitalization. Use when asked to write discharge instructions, go-home notes, post-op care, or medication instructions for a pet owner. Produces plain-language home-care instructions: medications (what/how much/when/how), activity restrictions, what to watch for, warning signs that mean call-now, the recheck plan, and emergency contacts — written so a worried owner can actually follow them.
日本語の概要は準備中です。原文の説明を表示しています。
Practise the structured interview (结构化面试) for Chinese civil service and public institution posts (公务员面试 / 事业单位面试): the common question types, a clear answer structure for each, timed mock rounds and feedback on content, structure and delivery. Use when asked 公务员面试怎么准备, 结构化面试题, 帮我模拟面试, 综合分析题怎么答, 应急应变题, or practise the civil service interview. Produces a question-type guide, answer frameworks with worked examples, a timed mock interview asked one question at a time, scored feedback, and a practice plan up to the interview date.
日本語の概要は準備中です。原文の説明を表示しています。
Run the pre-flight checklist before an agent drives a browser — the untrusted-web-content threat (every page is attacker-controllable), the credential and session-cookie exposure, the action-confirmation gates for purchases and posts, and the sandboxing that limits the damage. Use when asked let my agent browse safely, is it safe to give the agent computer/browser use, guardrails before the agent uses my browser, or review my browser agent's setup. Produces the sandbox decision, the content-injection defenses, the action gates, and the credential-isolation rules.
日本語の概要は準備中です。原文の説明を表示しています。
Write status updates people actually read — the traffic-light-plus-narrative format (state first, story second), the blockers-are-asks rule, and the skimmable structure that respects a reader with thirty seconds. Use when asked write my weekly update, format our team's status posts, nobody reads my updates, or what goes in a good async check-in. Produces the update format with a filled example, the blockers-as-asks discipline, and the reader-time contract.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a skill's recommendations into real, executed actions — open the tickets, file the issues, post the updates — safely: dry-run preview, risk-classified, approval-gated, then recorded back to the brain. Use when asked to act on a plan, file tickets from a checklist, create issues from a PRD, execute the recommended next steps, or wire a skill's output into GitHub/Linear/Slack. Produces a dry-run actions plan with per-action risk, executes only after approval via the connected action MCP, and logs what was done. Nothing acts silently.
日本語の概要は準備中です。原文の説明を表示しています。
Write clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare the conversations with aging parents that everyone postpones — the driving talk, the money talk, the care-options talk, the moving talk — each with an opener that doesn't ambush, a dignity-first script, rehearsal against realistic resistance, and the fallback when it goes badly. Use when someone says 'I need to talk to my dad about driving', 'my mum won't discuss her finances', 'we need to talk about care', or is dreading a visit for exactly this reason. Produces the conversation plan, a rehearsal, and the small-steps fallback. A preparation tool, not family therapy — and it says so when the situation needs more.
日本語の概要は準備中です。原文の説明を表示しています。