How to use the Adaptyv Bio Foundry API and Python SDK for protein experiment design, submission, and results retrieval. Use this skill whenever the user mentions Adaptyv, Foundry API, protein binding assays, protein screening experiments, BLI/SPR assays, thermostability assays, or wants to submit protein sequences for experimental characterization. Also trigger when code imports `adaptyv`, `adaptyv_sdk`, or `FoundryClient`, or references `foundry-api-public.adaptyvbio.com`.
database-lookup
database-lookup is an open-source data skill for Claude Code and compatible agents, published by K-Dense-AI. Its author describes it as: “Query documented public database APIs with explicit endpoints, filters, pagination, and provenance. Use when a scientific, regulatory, financial, or other database-backed fact must be retrieved reproducibly from a nam…”. The project has 34k stars on GitHub and is available under the MIT license. Add it to your setup with `git clone https://github.com/K-Dense-AI/scientific-agent-skills ~/.claude/skills/database-lookup`.
What database-lookup does
This skill catalogs 78 public databases with documented API access patterns. Your job is to turn the user's intent into a reproducible retrieval: select the authoritative database(s), make bounded and rate-limited API calls, verify counts when completeness matters, and return results with enough provenance that another agent or human can repeat the lookup.
Installation
Add database-lookup to your agent with:
git clone https://github.com/K-Dense-AI/scientific-agent-skills ~/.claude/skills/database-lookupAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for database-lookup is organised into these sections:
- Core Workflow
- Database Selection Guide
- Common Identifier Formats
- Identifier Resolution
- POST-Only APIs
- API Keys and Access Restrictions
- Databases requiring API keys (free registration)
- Databases with paid or restricted access
- Loading API keys
- Making API Calls
- Request guidelines
- Query Construction Safety
When to use it
Reach for database-lookup when you want data help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear MIT license — safe to read and adapt
- Ships in K-Dense-AI/scientific-agent-skills, an established project with 33,821 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does database-lookup do?
- Query documented public database APIs with explicit endpoints, filters, pagination, and provenance. Use when a scientific, regulatory, financial, or other database-backed fact must be retrieved reproducibly from a named source rather than inferred from general knowledge.
- How do I install database-lookup?
- Run git clone https://github.com/K-Dense-AI/scientific-agent-skills ~/.claude/skills/database-lookup in your agent, then reload your skills. Review the source at https://github.com/K-Dense-AI/scientific-agent-skills before installing.
- Is database-lookup free to use?
- Yes. database-lookup is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
- Where does database-lookup come from?
- database-lookup ships inside K-Dense-AI/scientific-agent-skills, a repository that contains 41 catalogued skills in total. The repository's 33,821 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Data →This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Plan, execute, and document validation, verification, and transfer of analytical procedures under the governing framework - ICH Q2(R2) and Q14, USP <1220>/<1225>/<1226>, ICH M10 bioanalytical, CLSI EP, or ISO/IEC 17025. Use for HPLC, LC-MS/MS, GC, CE, ICP-MS, dissolution, qNMR, qPCR, NIR, and ligand binding or cell-based assays whenever the question is whether a procedure is fit for its intended purpose. Triggers include "method validation", "analytical method validation", "AMV", "validation protocol", "acceptance criteria", "linearity", "reportable range", "accuracy and precision", "repeatability", "intermediate precision", "recovery", "LOD", "LOQ", "detection limit", "quantitation limit", "specificity", "robustness", "method transfer", "method comparison", "Deming", "Passing-Bablok", "Bland-Altman", "equivalence testing", "OOS investigation", "ICH Q2", "Q2(R2)", "Q14", "USP 1225", "ICH M10", "incurred sample reanalysis", "ISR", "CLSI EP", and any request to show that an assay works.
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Autonomously improve a real artifact (code, training recipe, agent harness, data pipeline, prompt) against an objective and an evaluator, using Hypothesis Tree Refinement (HTR) from the Arbor paper. Use this whenever someone wants to iteratively optimize something over many experiments without overfitting — e.g. "get my model's eval score up", "improve this agent/harness", "tune this pipeline", "beat the baseline on this benchmark", "run a search over approaches and keep the best", "do an MLE-bench / Kaggle-style optimization", or any long-horizon "make this artifact better and don't just memorize the dev set" task. Trigger it even when the user doesn't say "Arbor" or "hypothesis tree" but describes repeated experiment-and-evaluate loops, branching exploration of competing ideas, or worries about a dev/test gap. Runs Claude itself as the coordinator with subagent executors in isolated git worktrees; for the standalone `arbor` CLI tool see references/arbor-upstream.md.