1823 个 · 按相关度排序
AI-powered design review for Figma components with weighted dual-scoring system. Evaluates Style Guide Implementation (70%) and LLM Metadata Accessibility (30%). For export, hands off to atomic-design skill.
中文简介正在准备中。当前显示原文说明。
Create, revise, and validate publication-ready academic paper figures and tables. Use for LaTeX tables, related-work comparison tables, result tables, notation/dataset/taxonomy tables, precise source-data-driven experiment plots from CSV/JSON/logs, generated conceptual figures such as system overviews/pipelines/architectures/threat models, captions, artifact specs, source-data traceability, and paper-ready PDF/SVG/PNG/LaTeX exports. Do not use for prose-only paper writing, self-review, reviewer response, rebuttal drafting, or external literature-management workflows.
中文简介正在准备中。当前显示原文说明。
Analyze folders of Markdown/text research notes, Obsidian vaults, paper cards, invention notes, or memory exports as a practical knowledge map. Use when asked to find center topics, noisy or low-signal notes, possible contamination, overgrown topic groups, orphan notes, cleanup actions, or a useful public knowledge-hygiene workflow.
中文简介正在准备中。当前显示原文说明。
Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.
中文简介正在准备中。当前显示原文说明。
Scrub English drafts for AI tells before publishing. Use for any English LinkedIn post or newsletter draft right after composition and BEFORE export. Removes em-dash-as-pause, weak hedges, rule-of-three patterns, AI vocabulary, negative parallelisms, and inflated symbolism. Triggers on "polish", "humanize", "make this sound human", "/polisher", or after any English composer output. Leaves Arabic and Hebrew drafts untouched — humanizer-* skills handle those.
中文简介正在准备中。当前显示原文说明。
HTML-first persistent planning skill. Generates a single self-contained plan.html with interactive phases, drag-and-drop tickets, sliders, mockups, and embedded JSON state. Survives /clear via session catchup, tamper-protected by SHA-256, mirrors across 17 IDEs, ships 10 templates across Thariq's 9 categories, exports back to Markdown on demand. Use when asked to "plan it", "make me an html plan", "show me the plan", "render the plan", or when starting any multi-step task that needs a navigable artifact instead of a markdown wall.
中文简介正在准备中。当前显示原文说明。
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export.
中文简介正在准备中。当前显示原文说明。
AI-powered presentation generation via the 2slides API — create slides from text, match a reference image style, summarize documents into decks, add AI voice narration, and export pages/audio. Use for any "make slides", "create a deck", or "slides from this document" request.
中文简介正在准备中。当前显示原文说明。
Deploys and monitors ransomware canary files across critical directories using Python's watchdog library for real-time filesystem event detection. Places strategically named decoy files that mimic high-value targets (financial records, credentials, database exports) in locations ransomware typically enumerates first. Monitors for any read, modify, rename, or delete operations on canary files and triggers immediate alerts via email, Slack webhook, or syslog when interaction is detected, providing early warning before full encryption begins.
中文简介正在准备中。当前显示原文说明。
Systematically collects, categorizes, and distributes indicators of compromise (IOCs) during and after security incidents to enable detection, blocking, and threat intelligence sharing. Covers network, host, email, and behavioral indicators using STIX/TAXII formats and threat intelligence platforms. Activates for requests involving IOC collection, indicator extraction, threat indicator sharing, compromise indicators, STIX export, or IOC enrichment.
中文简介正在准备中。当前显示原文说明。
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks SolanaOS to add a note, list notes, search notes, or manage note folders.
中文简介正在准备中。当前显示原文说明。
Summarises one sprint from the board export, sprint report and review or stand-up notes the user provides into a one-page DRAFT sprint review summary: the sprint goal as written, items delivered, items not delivered with the reasons the sources state, carry-over, impediments, metrics exactly as given, and numbered questions for the retrospective, every row referenced to a work item or note fragment and every missing fact marked UNKNOWN. Use when the user asks to "summarise the sprint", "write the sprint review", "what did we deliver this sprint", "list the carry-over and blockers" or "draft the sprint recap". Do not use for the retrospective write-up or themed lessons across several sprints, use lessons-learned-synthesis instead; for a weekly project status report, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Drafts one weekly status update or team status email (done, in progress, blocked, next, asks) from the notes, task lists, tracker exports and messages the user attaches, pastes or makes reachable, every bullet traced to a source and every gap marked UNKNOWN, returned in the chat as Markdown for the user to review and send. Use when the user asks to "write my weekly status update", "draft the team status email", "turn my notes into a status report", "what did we get done this week", "summarise this week for my manager" or "prepare Friday's update". Do not use for maintaining a project's living logs or a project-level report built from them, use project-status-tracker instead. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Turns a schedule extract (milestone list or planning tool export) and the period's status notes into a DRAFT plain-language slip explanation: which milestones and activities slipped and by how many working days, arithmetic shown, why per the notes as verbatim fragments with source and date, what each slip pushes next per the extract, and the decision each slip needs framed as a question with the options the notes propose and the owner the governance documents name, every missing fact marked UNKNOWN. Use when the user asks to "explain the schedule slip", "what slipped this month and why", "write the schedule commentary for the steering pack", "put the delay in plain language for the sponsor" or "what decisions do these slips need". Do not use for the weekly status report, use project-status-tracker instead; for cost variances, use budget-variance-explainer; for one sprint's carry-over, use sprint-review-summary. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Turns a set of questions (form exports, helpdesk logs, meeting Q and A, chat threads, a plain list) plus the source documents the user supplies into a DRAFT FAQ grouped by theme: every answer quoted or paraphrased from a named source with a reference, verbatim quotes for dates, figures, eligibility and obligations, UNKNOWN where the sources are silent, a source register with precedence, a conflicts table and a routing list of unanswered questions to owners. Use when the user asks to "build an FAQ from these documents", "answer these questions from the policy", "turn the Q and A into an FAQ page", "group these questions and answer them from the guide" or "what do our documents say about these questions". Do not use for the manager FAQ of a changed HR policy, use policy-change-briefing instead; for checking whether a document's own claims are evidenced, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Triages a batch of customer support tickets (helpdesk export, shared mailbox, chat transcripts, web forms) into one row per ticket with category, urgency graded on the evidence in the ticket, suggested next action and owner, plus a DRAFT customer reply for every ticket that needs one, returned as one Markdown pack. Use when the user asks to "triage these tickets", "sort the support queue", "what needs an answer first", "categorise this backlog", "draft replies for these tickets" or "build today's queue review". Do not use for internal requests from colleagues, use request-intake-triage instead; for one long thread that needs handing over, use escalation-summary; for a personal mailbox, use inbox-triage. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Sorts a personal inbox backlog into five buckets (needs-reply-today, needs-reply-this-week, waiting-on-others, FYI, noise), writes DRAFT reply text for the messages that need an answer (up to 10 per run), and returns a dated triage report as one Markdown document. Lists moves or archives only as proposals for the user to perform, and only where a rule the user supplied says so; the agent changes nothing in the mailbox. Use when the user asks to "triage my inbox", "sort my mail", "clean up my inbox", "catch up after leave" or "what needs a reply today or this week". Do not use for a shared support queue or helpdesk export, use ticket-triage-pack instead; for what the user promised or is owed, use commitment-catcher; for one named thread, answer directly. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Reads a process flow diagram (image, PDF or native export) with its job header and returns a provenance-tagged extraction register: equipment, streams, tags, connectivity, instruments already shown, notes and legends, connectivity findings and an explicit UNKNOWN list, then holds at gate G1. Extracts and records only; never enriches, tags or proposes. Use when the user asks to "start a PFD to P&ID job", "read in the attached PFD", "extract the equipment and streams from this PFD" or "read this PFD into a register". Do not use for checking the model, use process-model-check instead; do not use to propose lines, instruments or tags, use piping-enrichment or instrumentation-and-control-enrichment after gate G2. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Reads one spreadsheet, CSV export or pasted table together with the user's question and drafts an insight pack: a data profile, observations cited to named columns and values and framed as leads, caveats, and suggested charts and follow-up analyses. Every figure carries the label "as read, verify in source"; correlation is never stated as causation. Use when the user asks to "profile this spreadsheet", "what does this data say", "find anomalies in this extract", "give me a first read on this CSV" or "summarise this table". Do not use for a purchase order log or spend extract, use purchase-order-anomaly-review instead; for actuals versus budget, use budget-variance-explainer instead; for a report that arrives by email on a schedule, use report-attachment-analyzer instead. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Prepares a DRAFT leadership-meeting briefing pack from the reports, meeting notes, emails and dashboard exports the user provides: one headline, metrics exactly as stated with period and source, decisions the meeting must take, risks as reported, talking points with anticipated questions, a source reference on every line and UNKNOWN where the material is silent. Use when the user asks to "brief the leadership team", "prepare the exec pack", "pull together a briefing for the steering committee", "summarise these reports for the CEO", "what do I tell the board on Monday" or "build the pre-read for the management meeting". Do not use for a formal board or committee paper seeking a resolution, use board-paper-skeleton instead; for a personal one-page prep drawn from the user's own calendar and inbox, use meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Turns an actuals-versus-budget extract (spreadsheet, export or pasted table) into a DRAFT variance table with absolute and percentage variances, favourable or adverse marking and a ranking by size, then drafts plain-language driver hypotheses for each material variance as questions to verify with a named owner, never as asserted causes. Use when the user asks to "explain these variances", "why are we over budget on this line", "write the variance commentary for the management pack", "actuals versus budget analysis" or "which lines drive the variance". Do not use for a dataset with no budget or comparison column, use dataset-insight-pack instead; for weekly operational figures against last week, use kpi-weekly-report-writer. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Reads a cash forecast (spreadsheet, model export, pasted table or the narrative that accompanies it) and returns a DRAFT assumptions sheet: every assumption the forecast rests on, stated or implied by the figures, with its value as read, its location in the model, the cash lines it drives, its stated source or "not stated", the evidence that would test it, an owner, and one neutral challenge question, so a reviewer can work through the assumptions one by one. Use when the user asks to "list the assumptions behind this cash forecast", "what is this cash flow forecast assuming", "prepare the challenge questions for the treasury review", "pull out the drivers of the 13-week cash forecast" or "build an assumptions register for the liquidity plan". Do not use for actuals against budget by line, use budget-variance-explainer instead; do not use for the case behind a capital request, use capex-request-pack instead. Drafts for human review; never approves, authorises or signs off.
中文简介正在准备中。当前显示原文说明。
Search academic references for a manuscript and export them to a verified refs CSV, then optionally hand off to cec-sheet. Claims are decomposed into conditions that define when to stop; references are found by keyword search (Mode A targeted / Mode B agentic via Codex CLI, run as two independent search routes) and by citation chaining (Mode C — backward refs, forward citations, similar articles, same author, and reference lists of OA full text/PDF, imozuru-style). All paths end in bundled deterministic tools (scripts/pubmed_search.py, scripts/citation_chain.py) that fetch bibliography live from PubMed, so PMIDs are never fabricated, and each supporting sentence is machine-verified verbatim against the fetched abstract. Triggers: "論文検索", "文献検索", "文脈検索", "コンテキスト検索", "原稿の引用を探して", "原典を探して", "芋づる", "引用をたどって", "被引用", "孫引き", "refs.csv", "codex-refs", "/codex-refs".
中文简介正在准备中。当前显示原文说明。
Load when creating or editing a Slidev `slides.md` developer talk/workshop with Markdown slides, Vue components, live code, Mermaid/LaTeX, presenter notes, or Slidev PDF/PPTX export; not for native PowerPoint decks or general docs.
中文简介正在准备中。当前显示原文说明。