216 skills · sorted by relevance
Comprehensive research corpus covering 40+ agentic coordination protocols and ecosystems (MCP, A2A, ANP, UCP, ACP, AGNTCY, NANDA, FIPA, WoT, etc.) with emphasis on identity architectures, governance bodies, and interoperability convergence patterns.
The English summary is being prepared. Showing the original description.
Voegt een proof-of-concept toe aan het poc-portaal op poc.regelrecht.rijks.app — register-entry, map-indeling, de subpad-aanpassingen die een losse app nodig heeft om onder /<slug>/ te draaien, en de bedrading in de deploy. Gebruik dit bij "voeg poc X toe", het verhuizen van een losse PoC-repo naar de monorepo, of het aanpassen van status en voorbehoud van een bestaande poc.
The English summary is being prepared. Showing the original description.
Scanpy is a scalable Python toolkit for analyzing single-cell RNA-seq data, built on AnnData. Apply this skill for complete single-cell workflows including quality control, normalization, dimensionality reduction, clustering, marker gene identification, visualization, and trajectory analysis.
The English summary is being prepared. Showing the original description.
Find biological pathways and functions enriched in gene lists or ranked gene data. Choose an appropriate statistical method, align gene identifiers, define comparison backgrounds, and turn results into interpretable tables and plots with multiple-testing corrections.
Prepare bulk RNA-seq sequencing files or quantification outputs for gene-level comparisons. Check sample information and data quality, configure processing workflows, and assemble validated count tables and metadata for downstream differential expression analysis with PyDESeq2.
Explore unfamiliar code with GitNexus to understand project structure and execution flows. Find related functions, inspect their callers and callees, and read implementation files to explain how a feature works, with repository and index freshness information.
Build and maintain a GitNexus code index, a searchable map of code relationships. Use CLI commands to refresh or remove indexes, check their status, list indexed projects, and generate repository documentation with an LLM.
Carry out an engineering plan through stepwise code changes, dependency impact checks, tests, and focused commits. It also handles small, bounded tasks directly, checking the code relationship index before relying on its results.
Review a GitNexus pull request for production readiness with seven coordinated reviewer agents. Combine their findings and have a final critic check the draft, producing a review without editing code or posting results.
Coordinate a development task from planning through implementation and review. Choose whether to proceed after seeing the plan, then receive a report covering commits, verification results, review findings, and any work left unfinished.
Rename functions, extract modules, and split or move code with dependency checks before editing and validation afterward. GitNexus previews semantic renames, meaning changes follow code bindings, and reports the scope and limits of its coverage.
Review pull requests, branches, commit ranges, or local changes with GitNexus. Combine code relationship analysis with source and test inspection to identify concrete defects, missing tests, affected behavior, and risks before merging.
Investigate errors and unexpected behavior by finding related code, following function calls, and checking source files. GitNexus helps trace execution paths, while the diagnosis identifies the repository and reports how current its code index is.
Find the right GitNexus tools and workflows for exploring code relationships. This reference explains available commands, graph queries, and resources, including how to check which branch an answer describes and whether its index is current.
Understand and extend GitNexus taint analysis, which tracks data from input sources to potentially dangerous operations. Use its implementation guidance to investigate missed or incorrect findings, add detection models, and validate analysis changes.
Assess the impact of code changes with GitNexus by tracing callers, dependencies, and affected execution flows. Check existing changes and report their scope, risk, and uncertainty before editing or committing.
Create an implementation plan grounded in code relationships and verified source files, with proposed changes, test scenarios, risks, and a structured handoff for an implementation agent. It can also revisit and strengthen an existing plan.
Use GitNexus to inspect which conditions control a statement and how variable values flow within a function. Understand early exits, investigate empty query results, and guide changes to the tool’s control and data dependency queries.
Draft an Amazon-style press release before development to clarify a product's customer value. Using Working Backwards, a method that starts with the intended customer outcome, organize the problem, benefits, and launch promise so stakeholders can assess the idea.
Guide a team through questions about users, workflows, and priorities to create a user story map. Organize activities and tasks, then define a minimum viable product and later releases that each cover the full workflow.
Track competitors' public pricing in a consistent format across repeated reviews. Compare prices, plans, feature access, usage limits, and free offers with previous records, then report documented changes and possible strategic signals with URLs and dates.
Estimate market size at three levels: total demand, the market your product can serve, and the share it could realistically capture. Use supplied figures or guided research to produce calculations with explicit assumptions, sources, and constraints.
Turn user research and complaints into a clear problem statement. Identify who is struggling, their desired outcome, barriers, root causes, constraints, and emotional impact, then summarize the problem in one sentence for team discussions or product planning.
Turn business goals and customer problems into a product roadmap. Define initiatives, rank priorities, check dependencies and team capacity, and organize releases with clear reasons stakeholders can review and discuss.