Loading...
Loading...
Found 1,118 Skills
Inspect an existing memory corpus (wiki substrate) and align it to this repo's Obsidian-friendly note-graph conventions. Use this when the user wants to import, normalize, retrofit, or clean up existing memory, notes folder, vault, docs tree, or mixed markdown knowledge base. In monorepos, also use it to align relevant AGENTS.md and CLAUDE.md files. Excludes goals/ from normalization. Not for routine wiki maintenance; use /loam::linting-memory for that.
Extract plain text from a document file - PDF, DOCX, XLSX, PPTX, RTF, or plain text/markdown/HTML. Use when a binary document needs to be turned into text, for example a contract PDF or an EHR DocumentReference attachment. Other skills (fhir) invoke scripts/extract.ts directly; the contracts MCP server bundles its own copy (servers/documents/src/extract.mjs) so its bundle stays self-contained — port fixes to both.
Summarizes Google Cloud Data Lineage graphs to help users debug data quality issues and understand data provenance for BQ/GCS. Use when summarizing upstream and downstream data flows, and presenting complex lineage data as an intuitive Markdown report. Don't use for generic BigQuery queries, editing lineage relationships, or downstream deprecation. Don't use for downstream blast-radius impact analysis (use datalineage-bigquery-asset-impact-analysis skill instead).
Apifox Import/Export and Quality Gate: Import OpenAPI/Postman/Apifox native formats, export OpenAPI/HTML/Markdown/Postman/Apifox native formats; Validate spec completeness, tags grouping, schema/body coverage before import, verify count, module and resource visibility after import.
Generate, refine, research, and validate startup ideas through an interactive founder-specific idea machine. Use when Codex needs to ask a few focused questions, search current public web signals, rapidly brainstorm startup or SaaS ideas, learn from love/maybe/no reactions, produce additional idea rounds, compare finalists, investigate competitors and existing workarounds, select a promising opportunity, or create an evidence-linked Markdown startup-idea report.
Generate the JSON config file that the Salesforce sandbox post-copy automation tool consumes, from a customer SOP in any format (PDF, xlsx, csv, JSON, docx, Markdown, plain text, or a screenshot of an endpoint table). Use when the user asks to create, build, generate, produce, or convert a post-copy or post-refresh automation config — turning a sandbox-refresh SOP into a JSON array of OutboundMessages and RemoteSiteSettings entries with ConfigurationName, Label, Fields, IsActive, and ExecutionOrder. Also trigger for phrasings like "post-copy config", "post-refresh automation JSON", "update the outbound message (OBM) endpoints after refresh", "convert this SOP to config", "remote site settings JSON", "refresh planner to JSON", or "sandbox refresh config". DO NOT TRIGGER when: user wants to deploy the generated config to an org (use platform-metadata-deploy) or execute/run the post-copy automation tool. This is the only skill for Salesforce sandbox post-copy config generation.
Author, scaffold, and run coding-agent-driven tests: Markdown case files executed by a coding agent against a live environment (browser, API, DB, logs, cloud, telemetry) with an auditable PASS/FAIL/BLOCKED report. Use when a deterministic test would be premature, brittle, too expensive, or too narrow.
Conduct deep research using NotebookLM integration — upload documents, query with citation-backed answers, synthesize findings, and produce infographic-style presentations. Output in Markdown, HTML/reveal.js slides, or Mermaid diagrams with visual hierarchy design specifications.
Create professional presentations using the Pyramid Principle methodology. Supports PPTX generation, Marp/Reveal.js Markdown slides, chart creation, speaker notes, and self-evaluation rubrics. Minimal intake form to rapid output workflow.
Grades a specified set of test methods individually and produces a concise table mapping each test (fully-qualified name) to a letter grade (A–F), a score band, and a one-line note — designed to be posted as a PR comment. Use when the caller wants per-test feedback on a curated list of methods (for example, the new or modified tests in a pull request), not a suite-wide audit. Polyglot: .NET, Python, TS/JS, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, C++. Input is a list of test methods (or method bodies / file+line spans); output is a compact markdown table plus a short summary. DO NOT USE FOR: full suite audits (use test-quality-auditor agent or test-anti-patterns), writing new tests (use code-testing-generator agent or writing-mstest-tests), fixing failures, or measuring code coverage.
A skill for writing and revising Japanese business documents to make them easy to read and understand. It can be used for creating and proofreading business documents such as meeting minutes (including transcribing to minutes), research/analysis reports, internal guides/manuals, research notes, discussion papers, proposals, reports, emails, and slide outlines, as well as following instructions like 'write from the conclusion', 'clarify the argument', 'keep headings concise', and 'explain technical terms in an easy-to-understand way'. It also supports removing AI-like tones (direct, indirect, or colloquial feedback such as 'AI-like', 'unnatural', 'make it more natural Japanese', 'mechanical', 'make it sound human', 'monotonous', or phrasing like 'it would be possible to...', as well as cases where the document was said to be written by AI or suspected of being so), improving hard-to-read or unclear sentences (such as incorrect word order, long sentences, unclear meaning, incorrect comma placement, etc.), writing new note articles, blog posts, and essays (including requests to write from scratch on any topic), rewriting and polishing existing sentences, diagnosing and scoring AI-like tones (requests without rewriting, such as 'Did AI write this?', 'Score the AI-like tone', 'Judge how AI-like this is'), and requests to learn and profile one's own writing style (including requests to write in one's own style by reading past sentences). It also addresses readability principles such as removing forbidden words, avoiding monotonous rhythm, homogeneous paragraph structure, literal translation of English syntax, as well as word order, commas, one meaning per sentence, and the distance between subject and predicate. The structuring of technical documents or formatting of Markdown itself (such as one sentence per line, quote blocks, footnote notation, etc.) is not covered—this falls under another skill, and this skill specializes in the naturalness, readability, and comprehensibility of text.
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.