「ida」の検索結果

Generic plugin system for Python applications. Auto-discovery, validation, fault tolerance. Zero dependencies (Python stdlib only).

日本語の概要は準備中です。原文の説明を表示しています。

Structured 6-step procedure for improving, renovating, or rebuilding existing pipelines, individual project folders, documentation structures, or software stacks. Addressable as "pipeline optimizer" (for whole topic pipelines, e.g. a software, research, or game-dev pipeline) or "project-folder optimizer" (for individual project folders within a pipeline, e.g. a single software tool or paper project). Triggers on tasks like "improve pipeline X", "optimize the stack", "rebuild Y", "renovation", "pipeline refactoring", "clean up project folder", "improve folder structure", "unify conventions", "documentation consolidation", "integrate into existing system", or any substantial intervention in established structures. Delivers building-stock analysis, purpose clarification, ideal sketch, gap plan, empirical pain-point identification, and retests with fresh subagents. Prevents parallel standards, duplication, and pipeline breaks.

日本語の概要は準備中です。原文の説明を表示しています。

Prüft bereitgestellte Formularbeschreibungen auf Struktur, Validierung, Verständlichkeit und Barrierefreiheit.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews marketing, packaging, web or sustainability text against the environmental-claim rules the user supplies (house policy, regulator guidance extract, industry code) and returns a DRAFT claims review: every environmental claim quoted verbatim with location and family, the evidence the text or evidence pack offers for it with date and scope, the supplied rule passages that bear on each claim, observations as read, and separate question lists for legal and for marketing. No compliance, greenwashing or substantiation verdict. Use when the user asks to "review these green claims", "check this copy against our environmental claims policy", "what evidence do we have for carbon neutral here", "list the sustainability claims in this brochure" or "prepare questions for legal on this eco campaign". Do not use for mapping general factual claims to evidence, use claims-evidence-map instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Converts a priced estimate spreadsheet into a DRAFT statement of work populated from the user's own SOW template, after checking that line items, hours, rates, subtotals and the grand total add up. Returns the populated SOW and a validation report as Markdown, flags every discrepancy and marks missing fields TBC. Use when the user asks to "turn this estimate into an SOW", "build the statement of work from the pricing workbook", "convert the quote into a scope document", "populate our SOW template from the estimate" or "draft the engagement document from the rate card". Do not use for reviewing or editing an existing SOW, use contract-review-pack instead; for a proposal before pricing is fixed use proposal-skeleton; for RFP or tender answers use rfp-response-drafter. 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 the text of a regulatory change (new regulation, amendment, rule, guidance or standard revision) into a DRAFT impact note: what changed against the prior text where supplied, who is affected as the text scopes it, an obligations table with dates and owners to confirm, and open interpretation questions for legal. States only what the text says; the rest is UNKNOWN. Use when the user asks to "brief legal on this new regulation", "list what we must do by when under this amendment", "compare the new standard with the version it replaces", "turn this directive into an obligations table" or "what does this rule mean for us". Do not use for assessing existing controls against a requirement set, use controls-gap-pack instead; for gapping a policy against a standard, use policy-gap-review. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews one SKILL.md against the format rules and returns a findings table: strict YAML front matter with exactly name and description, name equal to the folder, description as the trigger, the eight-heading skeleton, capability-neutral wording, safety boundaries. Each finding carries severity, rule identifier, location, quoted evidence and replacement text; the verdict READY, REVISE or BLOCKED is an apparent state and the owner decides. Use when the user asks to "review this SKILL.md", "check my skill file before upload", "lint this skill description", "validate the front matter of this skill" or "score this skill folder". Do not use to write an agent's instructions field, use agent-instructions-drafter instead; for injection or leakage exposures use agent-instructions-red-team; for launch tests use agent-evaluation-plan. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Turns an engineer's notes, a ticket history or a chat thread into a draft step-by-step runbook with preconditions, stop conditions, numbered steps with checks, verification, rollback and escalation, for the team to validate before use. Commands verbatim, placeholders marked, every gap UNKNOWN; never executes a step or fills a gap from general knowledge. Use when the user asks to "write a runbook from these notes", "turn this resolved ticket into a runbook", "document the steps we ran" or "check this runbook for gaps". Do not use for a business process without commands, use sop-drafter instead; for a knowledge article or known-error record, use knowledge-article-drafter; for the post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts a blameless incident postmortem (summary, impact, timeline, detection and response, contributing factors as candidates for review, action items) from an incident channel export, ticket notes and any alert or change records, with UNKNOWN for every fact the inputs do not contain. Never assigns blame, names a root cause or re-rates severity. Use when the user asks to "write the postmortem for this incident", "build the incident timeline from the chat export", "draft the post-incident review" or "turn this ticket and channel log into an incident report". Do not use for a knowledge article from the resolved ticket, use knowledge-article-drafter instead; for project retrospectives, use lessons-learned-synthesis; for data-breach impact and notification questions, use data-incident-impact-brief. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Flags where a P&ID draft raises a process safety question and points to the candidate evidence an engineer would review (HAZOP register, relief study, SIL assessment, isolation philosophy), as questions and quoted passages with UNKNOWN for missing documents, plus safety functions, relief devices and isolation requirements carried over as stated. Never rates, sizes, classifies, resolves or declares protection adequate. Use when the user asks to "write the process safety flags", "produce the process safety section of the P&ID enrichment", "list which protection questions this P&ID raises" or "map the HAZOP and relief study evidence to the draft" after gate G2, once the piping and instrumentation sections exist. Do not use for proposing loops, alarms or trips from the control philosophy, use instrumentation-and-control-enrichment instead; do not use for checking identifiers, use tagging-and-numbering. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Prepares a DRAFT management-of-change intake record from a change description (email, meeting note, marked-up drawing or request form): what changes from what to what and where, the identifiers named, the candidate affected documents matched against the register, the disciplines to consult with the reason for each, and the numbered questions reviewers must answer, with UNKNOWN wherever the description is silent. Prepares the record only: never approves, classifies the change, decides replacement in kind or makes any hazard or safety judgement. Use when the user asks to "raise an MoC for this", "prepare the change request intake", "which documents does this change touch", "who needs to review this change" or "draft the MoC form from this email". Do not use for tracking who owes information to whom across disciplines, use interface-register-builder instead. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and repair a kohya-style LoRA dataset before training. Use when the user asks to check, validate, inspect, fix, clean, 体检, or 修 a dataset, captions, or tags. Inspect image count, repeats and step budget, resolution and aspect buckets, duplicates, corrupt or non-RGB images, missing or empty captions, trigger consistency, and tag-frequency hygiene. Return a structural PASS, WARN, or FAIL report and apply only confirmed fix_dataset.py actions, dry-run first with displaced originals quarantined.

日本語の概要は準備中です。原文の説明を表示しています。

Build an Anima LoRA from a single-character or style name, from Danbooru collection through curation, section-ordered WD14 captions, dataset checks, confirmed training, fixed-seed checkpoint validation, and a staged Civitai draft. Use for requests such as make a LoRA of X, collect images and train a character LoRA, train and upload to Civitai, or build a dataset from scratch and publish. Delegate training to lora-trainer and structural checks to dataset-doctor; never train without confirmation and never auto-publish.

日本語の概要は準備中です。原文の説明を表示しています。

割り当てられたコード・設計・指示の対象を、指定された観点から実際に評価するための手順。担当配分・追加reviewer起動・結果の全体統合は行わない。

- Investigate an email address — MX and syntactic validation, Gravatar lookup, corporate email-format inference, breach exposure, and full mail-header analysis covering the Received chain, Message-ID and SPF, DKIM and DMARC results.

日本語の概要は準備中です。原文の説明を表示しています。

Weave a new node (concept, framework, theory, project, principle) into the whole vault graph rather than just creating a note. Mode A links one new node against the vault by top-K retrieval, with the LLM judging only those candidates; mode --deep finds orphaned islands and wires them in. Backup before edits, preview before writing. Triggers: "/relink", "integrate this concept".

日本語の概要は準備中です。原文の説明を表示しています。

Draft short, in-voice reply candidates to a fresh community shortlist: read the nightly detector report, pick posts in safe or opinion topics, pull a grounding snippet from the local corpus, and write the drafts. Drafts only, and the owner posts. Triggers: "/sostav-comments", "draft replies to the shortlist".

日本語の概要は準備中です。原文の説明を表示しています。

Finds high-value SEO and GEO keywords using web search, AI analysis, and optionally paid tools like Ahrefs or Semrush. Produces a validated keywords.csv file with a fixed schema for downstream pipeline consumption.

日本語の概要は準備中です。原文の説明を表示しています。

Cut background heat and noise on this machine: audit scheduled tasks by runs per hour, autostart entries, GPU holders, power plan and top CPU, then propose disable or stretch candidates, decide line by line with the operator and apply only approved lines. Triggers: /deflate, fan is loud, laptop runs hot, what can I turn off, machine slow from background load.

日本語の概要は準備中です。原文の説明を表示しています。

Work the comments under published posts in one pass: list unanswered ones, reply only where a reply is genuinely expected (at most three per pass), name top commenters as warm-DM candidates, and prepare reply drafts on approval. Triggers: "/comments", "unanswered comments", "who is commenting".

日本語の概要は準備中です。原文の説明を表示しています。

Verify SIPS proof surfaces before reporting completion. Use when asked to scan, verify, validate, prove, audit, or check whether a repo or SIPS install is coherent.

日本語の概要は準備中です。原文の説明を表示しています。

Single-mainline governance for deployless repositories. Use after a deployless audit when a repo needs trunk-based branch rules, branch protection, contribution guidance, review gates, merge queue policy, AI PR intake rules, or agent-ready mainline practices.

日本語の概要は準備中です。原文の説明を表示しています。

Remote-sensing literature search, citation verification, sensor/platform/dataset query strategy, citation file management (.ris/.bib/.enw conversion), and reference management (BibTeX, related articles, DOI/arXiv lookup) across CrossRef, arXiv, Scopus, ScienceDirect, Semantic Scholar, and domain web sources. Use when the user needs coordinated multi-step literature workflows for remote sensing, Earth observation, geospatial AI, GIScience, photogrammetry, SAR, hyperspectral imaging, LiDAR, satellite missions, benchmark datasets, land-cover mapping, change detection, object detection, segmentation, retrieval, or multimodal remote-sensing foundation models. Also trigger on general literature-search needs during academic writing even without the word "Nature", such as searching for papers/literature, doing a literature review, verifying a citation, converting citation files, and Chinese phrasings like 文献检索、查文献、找文献、 文献综述检索、查论文、引文核对、参考文献管理、文献去重.

日本語の概要は準備中です。原文の説明を表示しています。