Results for “microsoft-graph”

Scopes code-review blast radius and detects architectural hotspots using Tree-sitter AST analysis and GraphRAG, with an MCP server for graph-based analysis.

Generate, edit, and validate draw.io diagram files (.drawio) with correct mxGraph XML structure for flowcharts, architecture, sequence, ER, and UML diagrams.

Reference for querying the Atlas knowledge graph through its MCP tools — the SECONDARY enrichment/comparison layer that adds best-practice context to systems you have ALREADY scanned from your real sources (`az`, repos, dirs). Use when you need to look up nodes, edges, kinds, clusters, stats, or wiki pages in Atlas to compare against your real inventory. (atlas graph, query atlas, atlas mcp, search the graph, graph neighbors, atlas record, atlas kinds, enrichment layer)

List, export, and review Stata graphs from the current session.

When tackling a task that requires domain expertise beyond general coding ability — architecture patterns, framework-specific gotchas, deployment strategies, security anti-patterns, or specialized workflows — call the windags_skill_graft MCP tool with your task description. You'll receive expert knowledge including decision trees, failure modes, worked examples, and anti-patterns from a library of 503+ curated skills. Only graft when the task genuinely requires specialized knowledge. Simple tasks (rename a variable, fix a typo, format code) do not need grafting.

Content Factory Graphify wrapper. Use for codebase map, “where does X live”, how modules connect, architecture orientation, or when graphify.mdc applies. Query graphify-out/ before grepping or reading giant markdown brains. Does not replace Mem0, Hindsight, or product Memory Service RAG.

Token-efficient code review using Tree-sitter AST graphs and MCP. Reduces AI assistant token usage by 6.8–49x by computing blast radius of changes instead of reading entire codebases. Uses SQLite graph database for structural analysis.

Query the Yana AI codebase knowledge graph via codebase-memory-mcp. Use instead of grep/glob when exploring call chains, finding callers/callees, understanding architecture, or tracing impact of changes. Triggers on: 'who calls X', 'trace path', 'find callers', 'search graph', 'cbm', 'knowledge graph', 'what calls', 'call chain', 'what uses', 'where is X defined', 'architecture overview', 'impact of changing'.

Crea gráficos profesionales con Matplotlib, Seaborn y Plotly, desde exploración rápida hasta visualizaciones publicables, eligiendo el tipo de gráfico adecuado para cada historia de datos.

Add Adaptive Card response templates to MCP-based API plugins for visual data presentation in Microsoft 365 Copilot.

Causal inference framework for answering "does X cause Y?" beyond correlation. DoWhy (Microsoft Research) provides the identify-estimate-refute loop: define a causal graph (DAG), identify the causal effect using backdoor/frontdoor/instrumental variable criteria, estimate treatment effects with multiple estimators, and validate results with automated refutation tests. Use when: distinguishing causation from correlation, estimating treatment effects (ATE, ATT, CATE), designing and analyzing A/B tests with confounders, using instrumental variables, performing counterfactual reasoning ("what would have happened if..."), validating causal claims with sensitivity analysis, working with observational data where randomization is impossible, or any analysis where the question is "what is the CAUSAL effect of X on Y" rather than just "how do X and Y relate?"