Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
日本語の概要は準備中です。原文の説明を表示しています。
4,324 件 ・ 関連度順
概要と使いどころ
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
日本語の概要は準備中です。原文の説明を表示しています。
Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
日本語の概要は準備中です。原文の説明を表示しています。
A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
Performs set operations on genomic intervals - intersect (-wa/-wb/-wo/-wao/-loj/-c/-v/-u), subtract (-A), merge (-d, -c/-o), complement, cluster, multiinter, unionbedg, map, and groupby - with bedtools (CLI) and pybedtools/pyranges/bioframe (Python). Covers the sorted-input contract and the -sorted chromosome-order footgun, reciprocal/fractional overlap (-f/-F/-r/-e) and the A-vs-B asymmetry, -split for spliced/BED12/BAM features, and jaccard/fisher as mechanics only. Use when finding overlapping or unique regions between BED/peak/feature files, building consensus peaksets, removing blacklisted regions, transferring annotation values onto intervals, or computing interval-set similarity; route overlap-significance testing to overlap-significance.
日本語の概要は準備中です。原文の説明を表示しています。
Predict peptide-MHC class II (HLA-DR/DQ/DP) binding and presentation for CD4 T-cell epitopes with NetMHCIIpan-4.3 and MixMHC2pred-2.0. Covers why class II is far less reliable than class I (open binding groove, 9-mer register ambiguity, sparse noisy training data, DR>DP>DQ accuracy asymmetry), the DQ/DP heterodimer alpha/beta pairing trap, and the looser 1%/5% %Rank thresholds. Use when predicting CD4 epitopes for vaccine help, mapping class II neoantigens, or scoring long peptides against DR/DQ/DP. For CD8/class I see mhc-binding-prediction.
日本語の概要は準備中です。原文の説明を表示しています。
Delimits putative species boundaries from molecular data within the de Queiroz 2007 unified-lineage framework using ASAP (Puillandre 2021 successor to ABGD), mPTP C++ (Kapli 2017 successor to bPTP; bPTP is Python NOT R), GMYC single/multi-threshold (Pons 2006; Fujisawa 2013), multilocus BPP v4 with prior calibration from data (NOT defaults; Yang 2015), SNAPP + BFD* for SNP delimitation, DELINEATE (Sukumaran 2021) speciation-process modeling to address Sukumaran & Knowles 2017 PNAS critique that MSC delimits structure not species, integrative-taxonomy congruence (Padial 2010; Carstens 2013), Dsuite for introgression testing before sister claims (Malinsky 2021), and Meyer & Paulay 2005 barcoding-gap-absence caveat. Use when delineating species from DNA barcoding data, resolving cryptic complexes, choosing among ASAP/mPTP/BPP/DELINEATE, calibrating BPP priors, distinguishing introgression from ILS, or applying the Sukumaran-Knowles oversplitting correction.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses the quality and completeness of a genome annotation with BUSCO (conserved single-copy ortholog recovery), OMArk (proteome completeness, consistency, and contamination), CheckM2 (prokaryotic completeness/contamination), and a gene-set sanity panel (gene count, mono-exonic fraction, protein-length distribution, mRNA:gene ratio, coding density). Covers the assembly-BUSCO-vs-proteome-BUSCO diagnostic, what BUSCO-Duplicated really means, why gene count is a vanity metric, and the QC of transferred annotations. Use when judging whether an annotation is good enough to publish or submit, diagnosing a suspect annotation, or comparing annotation completeness across pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive quality control for CLIP-seq libraries (eCLIP, iCLIP, iCLIP2, PAR-CLIP) covering library complexity (preseq), FRiP, IDR replicate reproducibility, read-distribution metagene, SMInput vs IgG control rationale, rRNA / snoRNA contamination, fragment-length distribution, and ENCODE-compliance thresholds. Use when assessing whether a CLIP library passed, deciding lenient vs stringent peak thresholds, comparing replicates with IDR rescue and self-consistency ratios, or distinguishing failed IP from over-amplified library.
日本語の概要は準備中です。原文の説明を表示しています。
Build a differential-ready consensus peakset from per-replicate ATAC-seq peaks using iterative overlap removal, fixed-width re-centering, and majority-rule overlap. Use when generating a stable peak coordinate system for downstream differential accessibility, ML feature engineering, cross-sample comparison, or fixed-width peak counts; covers Corces 2018 iterative overlap (501 bp), DiffBind summit re-centering, and ENCODE consistency rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when selecting a TPR-registered Training Provider for behind-the-wheel ELDT training. Covers the registry, evaluation criteria, and common pitfalls.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to understand the International Registration Plan (IRP). Covers when you need to register apportioned, how it differs from IFTA, and quarterly fees.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about the FMCSA Drug & Alcohol Clearinghouse — full vs limited query, pre-employment vs annual query, query credit purchasing, who has access (employers, drivers, MROs, SAPs, state licensing agencies), reporting violations to the Clearinghouse, the "prohibited" status workflow, consent forms, or how to register/use the clearinghouse.fmcsa.dot.gov portal. Cite 49 CFR 382.701-727.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about Electronic Logging Device (ELD) compliance under 49 CFR 395.20-38 — ELD mandate, AOBRD vs ELD transition, ELD exemptions, ELD malfunctions, 8-day paper backup, ELD certification on FMCSA registered list, data file integrity, edits + annotations, driver portability, and how to handle ELD failures at roadside. Cite 49 CFR 395.20-395.38.
日本語の概要は準備中です。原文の説明を表示しています。
Refute-before-prove research discipline: automated counterexample sweeps before any formalization, meter-integrity audits for information-bound experiments, mutation-tested model checkers, pre-registered commit-or-cut gates for speculative directions, wrong-turn reporting, and numeric-claim provenance. Use when validating any new theorem, bound, equilibrium, or security claim; when building or trusting a checker, simulator, or experiment; or when deciding whether a speculative research direction lives or dies. NOT for exploratory brainstorming, product prioritization, writing style, or literature review.
日本語の概要は準備中です。原文の説明を表示しています。
Chooses and designs developer surfaces for an agentic product: SDK, CLI, MCP, GUI, API, webhooks, and pd tube-style listener/sender workflows. Use when deciding why a user belongs in an SDK versus CLI/MCP/GUI, planning Python SDK parity, or making agent invocation easy across languages. NOT for implementing the full SDK, generic API docs, or UI visual design.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in cluttering -- the lesser-known fluency disorder characterized by rapid/irregular speech rate, excessive disfluencies, and frequent ADHD comorbidity. Covers differential diagnosis from stuttering, assessment protocols, therapy approaches (rate control, self-monitoring, pragmatic awareness), technology-assisted intervention, and AI tools for people who clutter. Activate on 'cluttering', 'rapid speech disorder', 'speech rate too fast', 'speech disfluency not stuttering', 'disorganized speech', 'ADHD speech problems', 'cluttering vs stuttering', 'speech intelligibility', 'mazed speech', 'telescoping words'. NOT for stuttering-only treatment (overlap is common but they are distinct), hearing disorders, or voice disorders (pitch, resonance).
日本語の概要は準備中です。原文の説明を表示しています。
Design and build mathematically rigorous, high-density, interactive data graphics and streaming telemetry visualizations following Mike Bostock's D3.js and Observable methodologies. Use when crafting custom SVG/Canvas charts, reactive streaming time-series, multi-dimensional brush-and-link coordinates, small multiples, or topological swarm graphs. NOT for generic dashboard template clones, basic spreadsheet charts, or off-the-shelf low-effort wrapper libraries.
日本語の概要は準備中です。原文の説明を表示しています。
Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).
日本語の概要は準備中です。原文の説明を表示しています。
Safety-case design for always-on agents with episodic memory. Covers data hygiene, privacy and security risk surfaces, cost controls, scope, user dependency concerns, retention, incident containment, and responsible deployment evidence. It identifies hazards and asks for named controls, tests, owners, and residual uncertainty; it does not provide legal, clinical, youth-safety, or jurisdictional determinations. Activate on: "agent safety", "always-on agent privacy", "agent cost control", "persistent agent risks", "AI companion safety", "agent data hygiene", "runaway agent costs", "parasocial AI risk", "/always-on-agent-safety". NOT for: architecture design (use always-on-agent-architecture), input design (use always-on-agent-inputs), application brainstorming (use always-on-agent-applications), healthcare compliance specifically (use hipaa-compliance).
日本語の概要は準備中です。原文の説明を表示しています。
Frame multi-agent designs through explicit environment, autonomy, information, coordination, commitment, incentive, and verification assumptions. NOT for endorsing multi-agent architecture without need or claiming runtime correctness from conceptual methods.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture and systems design for agents that retain bounded state across sessions. Covers durable event history, owned state, derived memory, retrieval indexes, framework evaluation, recovery, deletion, and rebuild behavior. Uses constructed implementation examples and workload calibration rather than universal vendor, latency, similarity, retention, or cost claims. Activate on: "always-on agent", "persistent agent architecture", "episodic memory system", "agent memory design", "long-running agent", "stateful agent", "agent that remembers", "MemGPT architecture", "Letta deployment", "/always-on-agent-architecture". NOT for: choosing what data to feed the agent (use always-on-agent-inputs), brainstorming applications (use always-on-agent-applications), safety and privacy concerns (use always-on-agent-safety), general agentic patterns (use agentic-patterns).
日本語の概要は準備中です。原文の説明を表示しています。
Design or audit an agent identity, credential, session, continuity, and reputation plan. Use when attributed outcomes must survive key rotation, restart, recovery, or review; when choosing Elo, TrueSkill, a contextual bandit, or an LLM judge; and when making Sybil, newcomer, calibration, collusion, and evidence limits explicit. Produces a supplied-plan consistency audit, never proof of observed delivery, cryptographic identity, or live enforcement. NOT for proving personhood, global Sybil resistance, or an unobserved delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Declare an agentic application's interaction disclosure, state, context, capabilities, and effect-control boundaries. Use for a reviewable design specification and static consistency audit before implementation. NOT for proving that controls are deployed or enforced, exposing private chain-of-thought, selecting a model/router, or designing a multi-agent protocol.
日本語の概要は準備中です。原文の説明を表示しています。