Skip to main content
Exécutez n'importe quel Skill dans Manus
en un clic
suifei
Profil créateur GitHub

suifei

Vue par dépôt de 32 skills collectés dans 5 dépôts GitHub.

skills collectés
32
dépôts
5
mis à jour
2026-07-10
explorateur de dépôts

Dépôts et skills représentatifs

browser-setup
Spécialistes du support aux utilisateurs d'ordinateurs

浏览器环境配置技能 - 自动检测系统已安装的 Chrome/Chromium,或提供下载安装指引。支持 Linux/macOS/Windows 跨平台检测。

2026-03-08
docx
Éditeurs PAO

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a "report", "memo", "letter", "template", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

2026-03-08
pdf
Développeurs de logiciels

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

2026-03-08
pptx
Développeurs de logiciels

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); 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," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

2026-03-08
xlsx
Commis en comptabilité et en auditCommis de bureau généraux

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

2026-03-08
api-client
Développeurs de logiciels

使用 Bun.fetch 进行 HTTP API 调用。支持 GET/POST/PUT/DELETE、JSON 处理、请求头设置、超时控制。当用户需要调用 API、获取网络数据、测试 API 接口时使用。

2026-03-06
bun-test
Analystes en assurance qualité des logiciels et testeurs

测试 Bun 运行时功能。当用户要求测试 Bun、验证 Bun 安装、或执行 JavaScript 代码时使用。

2026-03-06
data-analyzer
Scientifiques des données

使用 Bun + SQL.js 进行数据分析。支持 SQL 查询、数据统计、聚合分析、数据可视化准备。当用户需要分析数据、执行 SQL 查询、生成统计报告时使用。

2026-03-06
Affichage des 8 principaux skills collectés sur 25 dans ce dépôt.
build
Développeurs de logiciels

/build — Gate 1.5, the construction layer after /spec. It reads the authoritative SPEC.md (+ .spec/ gates, Decision Log, knowledge) and constructs the code from it, regenerating the design/tasks plan EPHEMERALLY each run (never enshrined as a source of truth, so it can't drift). It closes construction only when each targeted requirement's acceptance holds AND the load-bearing gates are green (probes re-run). On a spec-vs-reality conflict it stops and routes back to /spec — it never silently edits the spec. Default surface: propose-then-apply with checkpoints. Resumable.

2026-07-10
spec
Développeurs de logiciels

/spec — the project's process-management Gate 1. One repeatable command (like /init, but for the living specification). The AI plays an expert requirements-elicitation analyst that turns your vague idea into a clear, feasible spec: it clarifies the vague through investigation, reflects your idea back organized, offers better views, and reports what's closed-loop vs not. Investigation IS research: it reads the material you point at, searches its own knowledge, the web, the project's own data, skills and MCP, reasons it through, and runs probes to verify load-bearing truths — then drives every decision to closure and writes one authoritative, feasible SPEC.md. It resolves everything it can on its own and registers the reasoning; it asks you only about genuine forks that evidence can't settle, or when it found a better option than the one you proposed. Use /spec to define, refine, reconcile, or lock down what a project should be — before construction.

2026-07-10
yolo
Développeurs de logiciels

/yolo — the autonomous construct-to-green loop on top of /build (Gate 1.5). It schedules a recurring loop (Claude Code's /loop → CronCreate when available; otherwise an inline cycle) that keeps running /build in autonomous-to-green mode, code-reviews each round's diff, fixes the verified findings, and TERMINATES ITSELF (CronDelete) when no buildable work remains — or stops early and hands back to the human when it hits a genuine fork, a spec conflict, or two ticks with no progress. It changes /build's PACE, never its RULES: SPEC.md stays authoritative, done = acceptance + green gates, conflicts still route to /spec. Use /yolo when you've reviewed the spec, trust the gates, and want construction to just run to green without babysitting each checkpoint.

2026-07-10
5 dépôts affichés sur 5
Tous les dépôts sont affichés