agentsclimarketplace

Repository metadata extraction

Skill HolobiomicsLab/asb-skill-collections/collections/metabolomics/v2/skills/repository-metadata-extraction

Use when when you need to inventory a collection of related web applications or tools distributed across multiple repositories, discover their live deployment URLs, trace their associated publications, and verify accessibility and metadata completeness.From its SKILL.md

Install
npx -y skills add HolobiomicsLab/asb-skill-collections --skill repository-metadata-extraction

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as CC-BY-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

9.3 KB, ~1.8k tokens by cl100k_base, as published. Nobody here has run it

repository-metadata-extraction

License: restricted — no clear open-source license detected for the underlying tool; verify licensing before commercial use or redistribution. <!-- asb-license-banner -->

Summary

Extract and validate domain-specific tool URLs, associated publications, and metadata from repository README files and source code repositories. This skill systematically discovers live web application endpoints, peer-reviewed or preprint publication links, and taxonomic/data coverage information from structured repository documentation.

When to use

When you need to inventory a collection of related web applications or tools distributed across multiple repositories, discover their live deployment URLs, trace their associated publications, and verify accessibility and metadata completeness. This is particularly valuable when a README lists multiple domain-specific or variant tools (e.g., microbeMASST, plantMASST, tissueMASST) and you need comprehensive, validated links for end-user or citation purposes.

When NOT to use

  • Input repository README is missing or inaccessible—cannot extract metadata without source documentation.
  • Tools listed in README are outdated or deprecated—verification will fail; use historical archives (Internet Archive) if currency cannot be assumed.
  • Publication links are incomplete or missing from README—extraction will produce null fields; do not invent DOIs or URLs.

Inputs

  • Repository README file (Markdown or plaintext)
  • GitHub repository URL or Zenodo deposit URL
  • Publication reference section or bibtex file from repository

Outputs

  • Structured inventory (CSV or JSON) with tool name, live URL, publication DOI, publication title, journal/platform, verification status
  • Accessibility validation report (HTTP status codes, timestamp)
  • Taxonomic or data coverage table (if applicable, e.g., lineage tables)

How to apply

Begin by cloning or retrieving the primary repository (e.g., via Zenodo DOI or GitHub URL). Locate and parse the README file for explicit listings of standalone web applications, typically found in a section such as 'Standalone Web Apps' or 'Tools Available'. For each tool listed, extract the live URL (e.g., https://masst.gnps2.org/microbemasst/). Cross-reference each tool entry with associated publication links in a dedicated 'Publications' or 'How to cite' section, recording DOI, journal, and publication status (peer-reviewed vs. preprint). Validate accessibility by performing HTTP HEAD or GET requests to confirm each URL responds with a 2xx status code. For tools with lineage or taxonomic coverage metadata (e.g., tables documenting Kingdom, Phylum, Class, etc.), extract and structure this information. Compile results into a structured CSV or JSON inventory with columns for tool name, live URL, publication DOI/link, publication title, journal/preprint platform, and verification timestamp.

Related tools

Examples

curl -I https://masst.gnps2.org/microbemasst/ && python -c "import csv; csv.DictWriter(open('masst_inventory.csv','w'), fieldnames=['tool','url','publication_doi','journal']).writeheader(); csv.DictWriter(open('masst_inventory.csv','a'), fieldnames=['tool','url','publication_doi','journal']).writerows([{'tool':'microbeMASST','url':'https://masst.gnps2.org/microbemasst/','publication_doi':'s41564-023-01575-9','journal':'Nature Microbiology'}])"

Evaluation signals

  • All listed tool URLs are accessible and return HTTP 200 status; verify via curl -I or requests library
  • Each tool name in the inventory matches the corresponding README entry exactly (case-sensitive); no typos or aliases introduced
  • Publication DOIs are valid and resolvable via crossref.org or doi.org; publication titles match official records
  • Taxonomic or data coverage metadata extracted matches the source table structure (e.g., Kingdom, Phylum, Class columns preserved with correct counts)
  • Inventory is complete: no tool listed in README is missing from the output; verify via row count comparison

Limitations

  • Zenodo deposits or GitHub repositories may be archived or deleted after publication; periodic re-validation is necessary to maintain link viability.
  • Publication links embedded in README may reference preprints (bioRxiv, medRxiv) that later transition to peer-reviewed journals; extraction captures the link as documented, not the final published version.
  • Some tools may have multiple versions or staging deployments (dev, staging, production); README may not clearly distinguish deployment environments; HTTP redirects should be followed and final endpoint recorded.
  • Batch search scripts (jobs.py) require specific Python version (3.10 per README) and may fail or succeed inconsistently with the Fast Search API; this skill extracts metadata only, not executable validation.

Evidence

  • [readme] This repository contains the code and data for the different domain-specific MASSTs currently under development in the Dorrestein Lab at UC San Diego. This includes microbeMASST, plantMASST, tissueMASST, microbiomeMASST, and foodMASST.: "This repository contains the code and data for the different domain-specific MASSTs currently under development"
  • [readme] Standalone Web Apps: 1. microbeMASST 2. plantMASST 3. tissueMASST 4. microbiomeMASST 5. foodMASST 6. metadataMASST: "Standalone Web Apps: 1. microbeMASST ... 6. metadataMASST"
  • [readme] Publications associated with the search tools: 1. microbeMASST - Nature Microbiology 2. plantMASST - bioRxiv: "Publications associated with the search tools: 1. microbeMASST - Nature Microbiology"
  • [readme] Within the folder lineages you can find the complete lineage information of each NCBI taxonomy IDs used in microbeMASST and plantMASST.: "Within the folder lineages you can find the complete lineage information of each NCBI taxonomy IDs"
  • [readme] The code for the different standalone web applications, which allow users to search one spectrum at a time, can be found in GNPS_MASST: "The code for the different standalone web applications, which allow users to search one spectrum at a time, can be found in GNPS_MASST"

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.