crawlora-org/crawlora-skills

supplier-sourcing-research

Discover and compare suppliers behind brands using Crawlora's ImportYeti company reports and public business websites.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/crawlora-org/crawlora-skills --skill supplier-sourcing-research

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Supplier sourcing research

Build a supplier shortlist with identifiable companies, observed trade evidence, product fit, and unresolved qualification questions. Shipment records establish observations, not manufacturing quality, available capacity, or willingness to sell.

Setup

Set CRAWLORA_API_KEY to your key from crawlora.net. Run the bundled scripts/crawlora.sh from this skill directory or by absolute path. It sends x-api-key to https://api.crawlora.net/api/v1; keep the key in the environment. Read reference/endpoints.md for the selected ImportYeti, search, and website-extraction tools.

Find and qualify suppliers

  1. Establish the product, reference brands, desired geography, and qualification

criteria. ImportYeti search is by company/supplier name; for a product-only brief, first identify relevant importers or brands through web search.

  1. Search /importyeti/search with q and optional 1-based page. Resolve names

against country, address, and official domain before assigning a result to a brand. Similar names and importer subsidiaries are not interchangeable.

  1. Inspect kind. Only company results chain into /importyeti/company?slug=....

Supplier results have no supplier-detail endpoint in this API. Use their returned search fields and public websites; do not feed a supplier slug to the company endpoint. An unknown/empty kind needs manual identity verification.

  1. From a company report, retain supplier names/slugs, country, product categories,

shipment counts, and relevant recent shipment descriptions. Preserve bill-of- lading IDs and dates when present. Search/report dates may use different day/month orders; retain ambiguous raw dates rather than silently swapping them. Keep url/source_url and collection time.

  1. Compare candidates within compatible coverage windows. Counts, TEU, weights,

containers, and estimated freight spend are different measures; do not treat them as product units, purchase value, or share of a brand's total sourcing. Deduplicate repeated shipment evidence by bill of lading where possible.

  1. Check shortlisted suppliers' official sites using Bing and /web/scrape or

/extract (flat JSON bodies). Separate claimed capabilities/certifications from independently verified facts. Record MOQ, lead time, certifications, capacity, and current availability as unknown unless directly supported.

sh
scripts/crawlora.sh /importyeti/search q=nike page=1
# Use a returned kind=company slug after checking the entity's identity:
# scripts/crawlora.sh /importyeti/company slug=RETURNED_COMPANY_SLUG

Evidence and output

Return supplier, country/address, observed customer relationship, relevant product evidence, shipment metric/date scope, official website, fit rationale, and open qualification questions. Link claims to reports or company pages. Label a freight forwarder or trading intermediary when evidence supports it; do not assume every named shipper operates a factory.

  • Public shipment coverage is incomplete. Missing air/land records, confidential

records, or alternate names can hide a relationship; absence is not proof of no trade. See ImportYeti's coverage notes.

  • Empty supplier/shipment tables may reflect extraction gaps. Report unavailable

detail rather than concluding the importer has no suppliers. HS codes are a selected upstream list, not a complete product or tariff classification.

  • Preserve masked contact fields. Use only publicly provided business channels;

preparing a shortlist does not send inquiries or initiate orders.

  • Bound search pages and report lookups. Stop at total_pages, no progress, or

the requested shortlist size. Back off on 429, retry transient 5xx once, stop on 401/403, and check application code before using data.

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
crawlora-org
Communauté

amazon-jobs-research

Researches Amazon.jobs postings via the Crawlora API — search Amazon's public careers site by keyword and/or job category, then pull any single posting's full description and qualifications by job id — returning clean JSON. Use when the user wants to search Amazon job openings, browse a specific Amazon job category, or fetch the detail for one Amazon job posting.

installations
1
GitHub Stars
0
Mis à jour
26 sept.
crawlora-org
Communauté

amazon-research

Researches products, prices, availability, and search suggestions on Amazon (amazon.com) using the Crawlora API, returning clean JSON. Use when the user asks to find a product on Amazon, look up an ASIN's price/details, or pull Amazon autocomplete/keyword suggestions — instead of scraping Amazon pages.

installations
1
GitHub Stars
0
Mis à jour
26 sept.
crawlora-org
Communauté

anime-manga-research

Researches anime and manga titles via the Crawlora API — search, title detail, characters, staff, recommendations, rankings, and airing schedules — returning clean JSON. Use when the user wants an anime/manga's details, cast/staff, similar titles, seasonal rankings, or what's currently airing.

installations
1
GitHub Stars
0
Mis à jour
26 sept.
crawlora-org
Communauté

app-market-opportunity-research

Research app-market opportunities using Crawlora app catalogs, historical charts, live store listings, release notes, reviews, and Google Trends. Use for app niche assessments, competitor maps, chart-movement analysis, and evidence-backed unmet-need hypotheses.

installations
1
GitHub Stars
0
Mis à jour
26 sept.