PostFn specialist -- designs/reviews the response-formatting function in an Endpoint_Set. One of 5 inference Fn-types. Called by /haipipe-end when intent references PostFn, response formatting, post-processing, or `post`.
原文の言語: 英語
メニュー
SkillsMP は jluo41/Tools から 184 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
収集済み skill 184 件中 40 件を表示しています。
PostFn specialist -- designs/reviews the response-formatting function in an Endpoint_Set. One of 5 inference Fn-types. Called by /haipipe-end when intent references PostFn, response formatting, post-processing, or `post`.
原文の言語: 英語
Run any Stage 6 endpoint work: routes intent to the right specialist across Fn-type, artifact-verb, develop-target, and deploy-target axes. Use for designing inference Fns, packaging Endpoint_Sets, training a build, local inference tests, or deploying…
原文の言語: 英語
Src2InputFn specialist -- designs/reviews the record->wire-payload function in an Endpoint_Set (serializes a ProcessedDF record into JSON the model can ingest). Platform-specific: one impl per deploy platform (SageMaker flat JSON vs Databricks…
原文の言語: 英語
Internal-execution EXECUTOR: runs the 4-phase lifecycle (Plan → Build → Execute → Report) on a task-folder, iterates it over a task-group, or dispatches to a type specialist to scaffold; the `qa` verb is its one question door (fn/qa.md). Trigger: task, task…
原文の言語: 英語
Open and run a BOARD: one topic, one source folder tree, and one markdown page per decision (Q) or lifecycle stage (S), generated into a browsable board/ site with an Index, one page per group, one page per Q/S file, and shared assets. Use when a topic has…
原文の言語: 英語
The VARIANT contract for a DESIGN brief Page: one page per design BRIEF, such as one message drafted for one group of people, with the audience, the goal, and the constraints stated in its Opening and one Content division per CANDIDATE artifact, side by side.…
原文の言語: 英語
The VARIANT contract for a DISPLAY unit Page: one page per display unit a paper or application ships, such as a figure, table, or diagram, mirroring the unit's folder (float, assets, caption, provenance) and carrying the human acceptance that no file in that…
原文の言語: 英語
The VARIANT contract for a LITERATURE evidence Page: an evidence page declaring `route: outward` in its metadata head, whose questions face OUTWARD, toward published knowledge. Its Content is organized BY EXECUTOR: one `### E<n> · <question>` division per…
原文の言語: 英語
The VARIANT contract for a MEETING Page: one page per conversation worth keeping, generated by cli/meetingpage.py from a dated note. It loads haipipe-board-page for the base frame and adds only what a record of talk needs: the cast, the dated record in the…
原文の言語: 英語
The VARIANT contract for a SECTION Page: one page per reader-ordered section unit of a paper or application, produced by a stage that runs once per unit. It loads haipipe-board-page for the base and haipipe-board-page-for-stage for the chain and gate, then…
原文の言語: 英語
The VARIANT contract for a Board's numbered Skill and Agent mirror Pages. It loads haipipe-board-page for the base frame and adds only what a mirror Page needs: an Opening that introduces a unit instead of asking a rhetorical question, the…
原文の言語: 英語
The VARIANT contract for a SLIDE Page: one page per deck, one Content division per talk BEAT, one embed and one accept row PER SLIDE inside the beat. Each division carries the beat's SOURCE half (outline and talk notes, usually extracted from section pages)…
原文の言語: 英語
The VARIANT contract for a Board's S-Family-unit stage pages, one Page per lifecycle stage of a paper or application across seed, resource, claims, venue, pitch, narrative, display, and section-edit. It resolves a Page to its own stage through the…
原文の言語: 英語
The VARIANT contract for a VALUE evidence Page: an evidence page declaring `route: inward` in its metadata head, whose questions face INWARD, toward results this project must produce. Its Content is organized BY EXECUTOR: one `### E<n> · <question>` division…
原文の言語: 英語
The VARIANT contract for a Board's numbered QBv venue Pages, one Page per submission target such as a journal, agency, or patent office. It loads haipipe-board-page for the base frame and adds three figures in fixed order, venue-indexed Content divisions, the…
原文の言語: 英語
THE one door for paper-lifecycle work: parse intent (venue + stage), resolve the stage contract from stages/index.yml, ensure the S page exists, and hand the page to haipipe-board-page. Each stage runs the ordered phases declared by its stage.md and stops…
原文の言語: 英語
Complete a subjective-labeling corpus after sealed evaluation by freezing a validated production policy, running preflight and idempotent labeling, routing risky items to humans or unresolved status, reconciling one terminal disposition per item, and…
原文の言語: 英語
Perform sealed final evaluation after calibration stops: freeze G*, authorize release of protected test items, collect blind human H/L/N gold, close registered executor predictions, and produce absolute, baseline-uplift, held-out-family, class, region,…
原文の言語: 英語
Initialize a human-grounded subjective-labeling project from a large text corpus, vague trait idea, and one human semantic authority. Reserve a sealed final test, embed the development corpus, draw a random 50–60-item Round 1 batch, conduct resumable…
原文の言語: 英語
Compatibility alias for the revised human-grounded calibration command. Use when a user says /sl-iterate, asks for another subjective-labeling iteration, or refers to the legacy iterate workflow; route to /sl-round and explain the new sealed-prelabel,…
原文の言語: 英語
Run or resume one human-grounded calibration round after G_1: retrieve a broad seven-region candidate pool, obtain sealed independent weak-LM prelabels, compose a challenge-plus-consensus-audit human batch, conduct blind human adjudication, optimize the…
原文の言語: 英語
Compatibility alias for validated corpus completion. Use when a user says /sl-scale or asks to batch-label the remaining corpus with the legacy scale workflow; route to /sl-complete and require sealed-test qualification, risk routing, terminal reconciliation,…
原文の言語: 英語
Read-only dashboard for a human-grounded subjective-labeling project. Shows lifecycle phase, open round, D_t/G_t, Session progress, audit and challenge evidence, seven-region coverage, stopping gates, sealed-test validity, executor scorecards, production…
原文の言語: 英語
Compatibility alias for sealed final evaluation. Use when a user says /sl-validate, asks whether the guideline or weak models are good enough, or invokes the legacy public-dataset validation command; route project validation to /sl-evaluate and keep optional…
原文の言語: 英語
Human-grounded workflow for labeling a large text corpus on a vague subjective trait while jointly refining H/L/N gold labels, seven diagnostic regions, a human-and-machine-readable guideline, sealed-test model scorecards, and production provenance. Use for…
原文の言語: 英語
Rebuild a multi-lane flight-record timeline of any Claude Code session (paper runs, task/discovery dispatch chains, replication tests) from its transcript + subagent transcripts. Lanes = spawn depth (session / task or discovery orchestrator / creator /…
原文の言語: 英語
Open the Intervention Console for an intervention folder. Use for `/haipipe-application`, `/haipipe-application enter <path>`, `/haipipe-application status [path]`, or when starting work in an existing intervention. GET-OR-CREATE: a missing path offers to…
原文の言語: 英語
Round management for the intervention lifecycle. Captures stakeholder/clinician review feedback, A/B test results, or iteration decisions into dated round folders. Triages todo items back to lifecycle stages. Modeled on the paper family's round stage…
原文の言語: 英語
The PAGE contract and router of a Board: one persistent Page combines a stable Page Type with a current Page Phase. It owns the shared frame, fixed section order, section obligations, machine write boundaries, evaluation contract, and the lifecycle vocabulary…
原文の言語: 英語
The DRAFT phase contract for any Board Page. DRAFT is the authority to define or reopen the Page's purpose, Aims, and promised shape for one round; it is not identified by an empty file, first typing, or adding text. Load haipipe-board-page first, then the…
原文の言語: 英語
The PROBE phase contract for any Board Page. PROBE's plain job: send one question the Page cannot answer out to a real source, and bring the answer back without letting the source learn what is at stake. In the layer's terms, PROBE owns a consequential…
原文の言語: 英語
The REVISE phase contract for any Board Page. REVISE improves the realization of the current round while the Page's purpose and Aims stay fixed; it may add, delete, move, or rewrite, so edit shape never distinguishes it from DRAFT. Load haipipe-board-page…
原文の言語: 英語
AI-illustration renderer of the display family: generate publication-quality academic concept figures (architecture/method/pipeline/taxonomy) through a local Codex app-server bridge that uses Codex native image generation. Use when user says "画架构图", "method…
原文の言語: 英語
HTML PPT Studio — author professional static HTML presentations in many styles, layouts, and animations, all driven by templates. Use when the user asks for a presentation, PPT, slides, keynote, deck, slideshow, "幻灯片", "演讲稿", "做一份 PPT", "做一份 slides", a…
原文の言語: 英語
THE SINGLE DOOR into a paper. Use for `/haipipe-paper`, `/haipipe-paper enter PAPER_PATH`, `/haipipe-paper status [paper-path]`, or when starting work in an existing paper folder. Resolves the paper root, GET-OR-CREATEs a missing path (confirm-gated,…
原文の言語: 英語
Orchestrator for the paper structure lifecycle (1-lifecycle). Routes to stage specialists across the venue-free/venue-aligned boundary: seed, resource, claims are venue-FREE; venue pins the journal; pitch, narrative, display, section-edit are venue-ALIGNED…
原文の言語: 英語
One door for every paper lifecycle stage: seed · resource · claims · venue · pitch · narrative · display · section-edit. Reads stages/index.yml, loads ONLY the requested stage's contract, and drives its declared phases. Trigger: 写 seed, 立项, resource, 我们有什么,…
原文の言語: 英語
Compile a paper-owned LaTeX target to PDF, fix build errors, and verify output. Resolves a specific `.tex`, the Display gallery at `0-lifecycle/3-display/4-display.tex`, or the paper's unnumbered master/`2-src/compile.sh`. Compilation never approves a Board…
原文の言語: 英語
Audit a paper folder against the layout contract: the delete test (rm -rf 0-* 1-* 2-* must leave a paper that still compiles), two numbered roots, direct S01–S10 lifecycle folders, nested S03/S04 topic probes, displays/ as the only home of an asset, sections/…
原文の言語: 英語
Build a tracked-changes PDF (latexdiff style) showing what changed between a baseline commit and the current working tree. Class-aware (INFORMS / ACM / IEEE / Springer LNCS / NeurIPS / ICML / Elsevier / generic article), with a scope-aware noise filter that…
原文の言語: 英語