Not in the top 1,000 by GitHub stars
Nimbleway/agent-skills
Agent skills that give AI agents live web data — search, scrape, and extract structured data with Extraction Templates and Web Search Agents, plus one-command business intelligence workflows. Plugin and MCP server for Claude Code, Cursor, Codex, and Grok.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/account-brief/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/account-discovery/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/account-enrichment/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/account-signals/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/brand-mention-monitor/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/company-deep-dive/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/competitor-intel/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/competitor-positioning/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/credit-risk/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/deal-sourcing/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/decision-maker-identification/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/due-diligence/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/healthcare-providers-enrich/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/healthcare-providers-extract/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/healthcare-providers-verify/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/kyc-screening/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/launch-monitor/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/local-places/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/market-finder/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/meeting-prep/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/nimble-databricks-data-products/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/nimble-web-expert/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/portfolio-monitoring/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/seo-intel/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
skills/talent-sourcing/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
1b98fc453d2d → 1b98fc453d2d
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1b98fc453d2d
No earlier version was observed for comparison.
Verified commit 1b98fc453d2d2c5b3cea763fb2992c3b7d772232
git clone --filter=blob:none --no-checkout https://github.com/Nimbleway/agent-skills.git .hotskills/nimbleway-agent-skills && git -C .hotskills/nimbleway-agent-skills checkout --detach 1b98fc453d2d2c5b3cea763fb2992c3b7d772232
# Copy each selected skill directory from .hotskills/nimbleway-agent-skills into .claude/skills/<skill-name>/Heat
1.5- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
- account-brief
skills/account-brief - account-discovery
skills/account-discovery - account-enrichment
skills/account-enrichment - account-signals
skills/account-signals - brand-mention-monitor
skills/brand-mention-monitor - company-deep-dive
skills/company-deep-dive - competitor-intel
skills/competitor-intel - competitor-positioning
skills/competitor-positioning - credit-risk
skills/credit-risk - deal-sourcing
skills/deal-sourcing - decision-maker-identification
skills/decision-maker-identification - due-diligence
skills/due-diligence - healthcare-providers-enrich
skills/healthcare-providers-enrich - healthcare-providers-extract
skills/healthcare-providers-extract - healthcare-providers-verify
skills/healthcare-providers-verify - kyc-screening
skills/kyc-screening - launch-monitor
skills/launch-monitor - local-places
skills/local-places - market-finder
skills/market-finder - meeting-prep
skills/meeting-prep - nimble-databricks-data-products
skills/nimble-databricks-data-products - nimble-web-expert
skills/nimble-web-expert - portfolio-monitoring
skills/portfolio-monitoring - seo-intel
skills/seo-intel - talent-sourcing
skills/talent-sourcing
How it works
account-brief
When your agent uses it
Writes a dated, sourced brief on one company before a sales meeting: what they do, priorities, challenges, changes in the last 90 days, key people and talking points, using the Nimble `account-brief` agent template on live web data. Use when the user says "prep me for a meeting with", "account research on", "brief me on [company] before my call", "account brief", "what should I know before meeting", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use for researching the people attending (use meeting-prep), for an investment memo (use due-diligence), or for a list of changes since a date (use account-signals).
What it loads into context
Frontmatter
520 tokensAlways available to the agent
SKILL.md
2,193 tokensWhen the skill is activated
Reference documents
419,416 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Scripts executed separately
../nimble-databricks-data-products/scripts/build_dashboard.py../nimble-databricks-data-products/scripts/ingest.sh
Files
../../.claude-plugin/marketplace.jsonasset2,043 bytes../../.claude-plugin/plugin.jsonasset1,017 bytes../../agents/nimble-analyst.mddoc2,366 bytes../../agents/nimble-analyst.mddoc2,366 bytes../../agents/nimble-researcher.mddoc1,478 bytesSKILL.mdcore8,513 bytesSKILL.mdcore8,513 bytesSKILL.mdcore8,513 bytes../account-discovery/SKILL.mddoc8,568 bytes../account-enrichment/SKILL.mddoc8,589 bytes../account-signals/SKILL.mddoc8,350 bytes../brand-mention-monitor/SKILL.mddoc25,826 bytes../brand-mention-monitor/example.htmlasset62,826 bytes../brand-mention-monitor/references/memory-and-distribution.mddoc22,058 bytes../brand-mention-monitor/references/nimble-playbook.mddoc37,015 bytes../brand-mention-monitor/references/profile-and-onboarding.mddoc9,344 bytes../brand-mention-monitor/references/sources.mddoc7,840 bytes../brand-mention-monitor/references/template.htmlasset58,341 bytes../company-deep-dive/SKILL.mddoc13,706 bytes../company-deep-dive/references/dimension-agent-prompt.mddoc5,089 bytes../company-deep-dive/references/memory-and-distribution.mddoc22,058 bytes../company-deep-dive/references/nimble-playbook.mddoc37,015 bytes../company-deep-dive/references/profile-and-onboarding.mddoc9,344 bytes../competitor-intel/SKILL.mddoc15,075 bytes../competitor-intel/references/competitor-agent-prompt.mddoc3,051 bytes../competitor-intel/references/memory-and-distribution.mddoc22,058 bytes../competitor-intel/references/nimble-playbook.mddoc37,015 bytes../competitor-intel/references/profile-and-onboarding.mddoc9,344 bytes../competitor-positioning/SKILL.mddoc17,184 bytes../competitor-positioning/references/memory-and-distribution.mddoc22,058 bytes../competitor-positioning/references/nimble-playbook.mddoc37,015 bytes../competitor-positioning/references/positioning-agent-prompt.mddoc5,903 bytes../competitor-positioning/references/positioning-snapshot-format.mddoc1,719 bytes../competitor-positioning/references/profile-and-onboarding.mddoc9,344 bytes../credit-risk/SKILL.mddoc8,422 bytes../deal-sourcing/SKILL.mddoc8,476 bytes../decision-maker-identification/SKILL.mddoc8,647 bytes../due-diligence/SKILL.mddoc8,335 bytes../healthcare-providers-enrich/SKILL.mddoc15,324 bytes../healthcare-providers-enrich/references/memory-and-distribution.mddoc22,058 bytes../healthcare-providers-enrich/references/nimble-playbook.mddoc37,015 bytes../healthcare-providers-enrich/references/profile-and-onboarding.mddoc9,344 bytes../healthcare-providers-enrich/references/provider-extraction-patterns.mddoc6,868 bytes../healthcare-providers-enrich/references/wsa-reference.mddoc6,385 bytes../healthcare-providers-extract/SKILL.mddoc13,903 bytes../healthcare-providers-extract/references/memory-and-distribution.mddoc22,058 bytes../healthcare-providers-extract/references/nimble-playbook.mddoc37,015 bytes../healthcare-providers-extract/references/profile-and-onboarding.mddoc9,344 bytes../healthcare-providers-extract/references/provider-extraction-patterns.mddoc6,868 bytes../healthcare-providers-extract/references/wsa-reference.mddoc7,457 bytes../healthcare-providers-verify/SKILL.mddoc18,043 bytes../healthcare-providers-verify/references/memory-and-distribution.mddoc22,058 bytes../healthcare-providers-verify/references/nimble-playbook.mddoc37,015 bytes../healthcare-providers-verify/references/npi-verification-patterns.mddoc10,201 bytes../healthcare-providers-verify/references/profile-and-onboarding.mddoc9,344 bytes../healthcare-providers-verify/references/provider-extraction-patterns.mddoc6,868 bytes../healthcare-providers-verify/references/wsa-reference.mddoc6,238 bytes../kyc-screening/SKILL.mddoc8,362 bytes../launch-monitor/SKILL.mddoc25,387 bytes../launch-monitor/references/memory-and-distribution.mddoc22,058 bytes../launch-monitor/references/nimble-playbook.mddoc37,015 bytes../launch-monitor/references/profile-and-onboarding.mddoc9,344 bytes../launch-monitor/references/sources.mddoc12,099 bytes../launch-monitor/references/template.htmlasset28,659 bytes../local-places/SKILL.mddoc16,930 bytes../local-places/references/memory-and-distribution.mddoc22,058 bytes../local-places/references/nimble-playbook.mddoc37,015 bytes../local-places/references/profile-and-onboarding.mddoc9,344 bytes../local-places/references/wsa-pipeline.mddoc7,193 bytes../market-finder/SKILL.mddoc19,053 bytes../market-finder/references/audit-mode.mddoc7,611 bytes../market-finder/references/memory-and-distribution.mddoc22,058 bytes../market-finder/references/nimble-playbook.mddoc37,015 bytes../market-finder/references/profile-and-onboarding.mddoc9,344 bytes../market-finder/references/vertical-presets.mddoc6,513 bytes../meeting-prep/SKILL.mddoc24,374 bytes../meeting-prep/references/attendee-agent-prompt.mddoc4,545 bytes../meeting-prep/references/memory-and-distribution.mddoc22,058 bytes../meeting-prep/references/nimble-playbook.mddoc37,015 bytes../meeting-prep/references/profile-and-onboarding.mddoc9,344 bytes../nimble-databricks-data-products/SKILL.mddoc10,395 bytes../nimble-databricks-data-products/assets/nimble-logo.pngasset25,427 bytes../nimble-databricks-data-products/references/app-cookbook.mddoc4,795 bytes../nimble-databricks-data-products/references/branding.mddoc2,447 bytes../nimble-databricks-data-products/references/dashboard-cookbook.mddoc5,919 bytes../nimble-databricks-data-products/references/databricks-skills.mddoc1,944 bytes../nimble-databricks-data-products/references/install-nimble-integration.mddoc2,544 bytes../nimble-databricks-data-products/references/nimble-agents.mddoc11,840 bytes../nimble-databricks-data-products/references/preflight.mddoc3,425 bytes../nimble-databricks-data-products/scripts/build_dashboard.pyruns13,611 bytes../nimble-databricks-data-products/scripts/ingest.shruns2,390 bytes../nimble-web-expert/README.mddoc4,574 bytes../nimble-web-expert/SKILL.mddoc24,279 bytes../nimble-web-expert/references/batch-patterns.mddoc10,912 bytes../nimble-web-expert/references/error-handling.mddoc8,199 bytes../nimble-web-expert/references/nimble-agents/reference.mddoc21,365 bytes../nimble-web-expert/references/nimble-crawl/reference.mddoc7,011 bytes../nimble-web-expert/references/nimble-extract-templates/reference.mddoc6,389 bytes../nimble-web-expert/references/nimble-extract/browser-actions.mddoc10,910 bytes../nimble-web-expert/references/nimble-extract/browser-investigation.mddoc6,665 bytes../nimble-web-expert/references/nimble-extract/network-capture.mddoc8,487 bytes../nimble-web-expert/references/nimble-extract/parsing-schema.mddoc10,283 bytes../nimble-web-expert/references/nimble-extract/reference.mddoc15,979 bytes../nimble-web-expert/references/nimble-map/reference.mddoc3,967 bytes../nimble-web-expert/references/nimble-search/reference.mddoc8,479 bytes../nimble-web-expert/references/nimble-search/search-focus-modes.mddoc6,626 bytes../nimble-web-expert/references/nimble-tasks/reference.mddoc7,096 bytes../nimble-web-expert/references/recipes.mddoc6,906 bytes../nimble-web-expert/rules/nimble-web-expert.mdcasset3,827 bytes../nimble-web-expert/rules/output.mddoc1,123 bytes../nimble-web-expert/rules/setup.mddoc6,591 bytes../portfolio-monitoring/SKILL.mddoc8,390 bytes../seo-intel/SKILL.mddoc5,285 bytes../seo-intel/references/ai-platform-profiles.mddoc11,542 bytes../seo-intel/references/ai-visibility-agent-prompt.mddoc6,300 bytes../seo-intel/references/audit-agent-prompt.mddoc3,884 bytes../seo-intel/references/content-gap-agent-prompt.mddoc5,783 bytes../seo-intel/references/github-seo-checks.mddoc12,044 bytes../seo-intel/references/keyword-research-agent-prompt.mddoc2,990 bytes../seo-intel/references/memory-and-distribution.mddoc22,058 bytes../seo-intel/references/nimble-playbook.mddoc37,015 bytes../seo-intel/references/profile-and-onboarding.mddoc9,344 bytes../seo-intel/references/seo-audit-checks.mddoc15,437 bytes../seo-intel/references/seo-extraction-prompt.mddoc6,923 bytes../seo-intel/references/serp-query-patterns.mddoc6,551 bytes../seo-intel/references/wf-ai-visibility.mddoc20,160 bytes../seo-intel/references/wf-competitor-keywords.mddoc19,283 bytes../seo-intel/references/wf-content-gap.mddoc18,407 bytes../seo-intel/references/wf-github-seo.mddoc16,088 bytes../seo-intel/references/wf-keyword-research.mddoc18,701 bytes../seo-intel/references/wf-rank-tracker.mddoc15,237 bytes../seo-intel/references/wf-site-audit.mddoc15,167 bytes../talent-sourcing/SKILL.mddoc10,960 bytes../talent-sourcing/references/memory-and-distribution.mddoc22,058 bytes../talent-sourcing/references/nimble-playbook.mddoc37,015 bytes../talent-sourcing/references/profile-and-onboarding.mddoc9,344 bytes
Read SKILL.md
# Account brief
Writes a dated, sourced brief on one company before a sales meeting: what they do, priorities, challenges, changes in the last 90 days, key people and talking points.
User request: $ARGUMENTS
## What the user gets
A short brief: what the company does, current priorities and challenges with evidence, what changed in the last 90 days, key people, and talking points. Every item is dated and sourced.
## Agent template
This skill runs the Nimble gallery template `account-brief`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHubaccount-discovery
When your agent uses it
Builds a list of companies that match an ideal customer profile (ICP), each with the reason it fits and a source, using the Nimble `account-discovery` agent template on live web data. Use when the user says "find companies like", "build a prospect list", "ICP list", "find accounts that match", "target account list", "companies that fit our ICP", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use to research one known company (use account-brief) or to find investment targets (use deal-sourcing).
What it loads into context
Frontmatter
490 tokensAlways available to the agent
SKILL.md
2,206 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Files
SKILL.mdcore8,568 bytesSKILL.mdcore8,568 bytesSKILL.mdcore8,568 bytes
Read SKILL.md
# Account discovery
Builds a list of companies that match an ideal customer profile (ICP), each with the reason it fits and a source.
User request: $ARGUMENTS
## What the user gets
A list of companies that match the profile. Each row has the company name, website, why it fits, and a source.
## Agent template
This skill runs the Nimble gallery template `account-discovery`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHubaccount-enrichment
When your agent uses it
Fills a CRM record for a company from its domain: firmographics, current leadership, tech stack and funding, every field cited or left empty, using the Nimble `account-enrichment` agent template on live web data. Use when the user says "enrich these domains", "fill my CRM", "firmographics for", "enrich this account list", "what tech stack does", "company data for", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use to find who holds a specific role (use decision-maker-identification) or for a meeting brief (use account-brief).
What it loads into context
Frontmatter
502 tokensAlways available to the agent
SKILL.md
2,213 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Files
SKILL.mdcore8,589 bytesSKILL.mdcore8,589 bytesSKILL.mdcore8,589 bytes
Read SKILL.md
# Account enrichment
Fills a CRM record for a company from its domain: firmographics, current leadership, tech stack and funding, every field cited or left empty.
User request: $ARGUMENTS
## What the user gets
One record per company: legal name, HQ, founded, employees, industry, ownership, leadership, tech stack and funding. Each field has a source, or is left empty with a reason.
## Agent template
This skill runs the Nimble gallery template `account-enrichment`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHubaccount-signals
When your agent uses it
Lists what changed at an account since a date: funding, exec moves, launches, pricing changes and hiring pushes, each dated and cited, using the Nimble `account-signals` agent template on live web data. Use when the user says "what changed at", "buying signals", "track my accounts", "any news on my accounts since", "trigger events", "signals for", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use for a full company brief (use account-brief) or for investment holdings (use portfolio-monitoring).
What it loads into context
Frontmatter
490 tokensAlways available to the agent
SKILL.md
2,155 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Files
SKILL.mdcore8,350 bytesSKILL.mdcore8,350 bytesSKILL.mdcore8,350 bytes
Read SKILL.md
# Account signals
Lists what changed at an account since a date: funding, exec moves, launches, pricing changes and hiring pushes, each dated and cited.
User request: $ARGUMENTS
## What the user gets
Only events dated after the since date, each with date, type, headline, summary and source. If nothing changed, an empty list and the sources it checked.
## Agent template
This skill runs the Nimble gallery template `account-signals`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHubbrand-mention-monitor
When your agent uses it
Scans Reddit, X, LinkedIn, Instagram, TikTok, YouTube, blogs, news, and review platforms for brand mentions — scoring each across four dimensions (reach, velocity, sentiment, and risk-topic match) so teams can respond before one spirals. Sources adapt to the market: B2B brands weight LinkedIn, G2, and trade press; consumer brands weight TikTok, Instagram, and YouTube. Each is bucketed into Crisis / Watch / Engage / Log with a suggested owner and response window. Use when asked to "monitor brand mentions", "scan for brand mentions", "what are people saying about [brand]", "brand monitoring", "social listening", "run a brand sweep", "find high-risk mentions", or any variation of brand monitoring across web and social. Do NOT use for one-time company research or due diligence — use company-deep-dive instead. Do NOT use for competitor messaging/positioning analysis — use competitor-positioning instead. Do NOT use for funding/hiring/business signals on a competitor — use competitor-intel instead.
What it loads into context
Frontmatter
345 tokensAlways available to the agent
SKILL.md
6,191 tokensWhen the skill is activated
Reference documents
18,703 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Onboarding message
- Preflight
- How to start
- Step 0 — Source profile (market-specific, not fixed list)
- Step 1 — Mention sweep
- Step 2 — Scoring each mention (four dimensions)
- Step 2.5 — Memory dedup (filter already-known mentions)
- Step 3 — Tier assignment and routing
- Output template (REQUIRED)
- Source URL rule
- Distribution
- Saved preferences
- Re-run behavior
- End-of-run next steps
Files
SKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesSKILL.mdcore25,826 bytesexample.htmlasset62,826 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytesreferences/sources.mddoc7,840 bytesreferences/template.htmlasset58,341 bytes
Read SKILL.md
# Brand Mention Monitor
Scans the web and social media for brand mentions, scores each one on reach, velocity, sentiment, and risk-topic match, and surfaces the ones that need attention — bucketed into Crisis / Watch / Engage / Log with a suggested owner.
---
## Onboarding message
When this skill is triggered for the first time in a session, send this message:
> 👋 **Brand Mention Monitor is ready.**
>
> This skill scans Reddit, X, LinkedIn, Instagram, TikTok, YouTube, blogs, news, and review platforms for mentions of your brand — scoring each one across reach, velocity, sentiment, and risk so you see what matters before it spirals, and telling you exactly who should respond and how fast.
>View the complete source on GitHubcompany-deep-dive
When your agent uses it
Use this skill ANY TIME the user asks about a specific company. Triggers: "tell me about [company]", "research [company]", "what does [company] do", "who is [company]", "look up [company]", "company deep dive", "due diligence on [company]", "background on [company]", "dig into [company]", "analyze [company]", or evaluating a company for investment, partnership, or sales. MUST be used instead of answering from memory — fetches real-time web data (funding, leadership changes, product launches, news) your training data lacks. Use even for well-known companies. Produces a sourced 360° report covering funding, leadership, product/tech, market position, news, and strategic outlook with dates and URLs. Do NOT use for multi-company competitor monitoring (use competitor-intel) or meeting prep with attendees (use meeting-prep).
What it loads into context
Frontmatter
325 tokensAlways available to the agent
SKILL.md
3,234 tokensWhen the skill is activated
Reference documents
17,988 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Agent Teams Mode (Dual-Mode)
- What This Skill Is NOT
- Error Handling
Files
SKILL.mdcore13,706 bytesSKILL.mdcore13,706 bytesSKILL.mdcore13,706 bytesSKILL.mdcore13,706 bytesSKILL.mdcore13,706 bytesSKILL.mdcore13,706 bytesSKILL.mdcore13,706 bytesreferences/dimension-agent-prompt.mddoc5,089 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytes
Read SKILL.md
# Company Deep Dive
360° company research powered by Nimble's web data APIs.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
---
## Instructions
### Step 0: PreflightView the complete source on GitHubcompetitor-intel
When your agent uses it
Searches the live web via Nimble APIs to monitor competitors and produce a structured intelligence briefing. Runs parallel searches for news, product launches, hiring signals, and funding — then compares against previous findings to highlight only what's new. Use this skill when the user asks about competitors, competitive intelligence, or what rival companies are doing. Common triggers: "what are my competitors doing", "competitor update", "competitor news", "competitive landscape", "market intel", "what's new with [company]", "track [company]", "competitor briefing", "who's making moves", "competitive analysis", "losing deals to [company]", "battlecard". Also use before board meetings or strategy sessions when the user wants competitive context. Requires the Nimble CLI (nimble search, nimble extract) for live web data. Do NOT use for single-company deep dives (use company-deep-dive), meeting prep with attendees (use meeting-prep), or non-business queries.
What it loads into context
Frontmatter
342 tokensAlways available to the agent
SKILL.md
3,637 tokensWhen the skill is activated
Reference documents
17,480 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Agent Teams Mode (Dual-Mode)
- Error Handling
Files
SKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesSKILL.mdcore15,075 bytesreferences/competitor-agent-prompt.mddoc3,051 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytes
Read SKILL.md
# Competitor Intelligence
Real-time competitive intelligence powered by Nimble's web data APIs.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
---
## Instructions
### Step 0: PreflightView the complete source on GitHubcompetitor-positioning
When your agent uses it
Tracks how competitors position themselves online — scrapes homepages, features, pricing, and blogs to extract messaging, value props, CTAs, and pricing models. Compares against previous snapshots to surface positioning shifts with before/after tracking. Produces messaging matrices, content gap analysis, white space maps, and battlecard inputs. Use when anyone asks about competitor messaging, positioning, website copy, content strategy, or how competitors present themselves. Triggers: "competitor positioning", "messaging comparison", "content gap", "what changed on their site", "competitor homepage", "landing page teardown", "marketing battlecard", "how do they describe their product", "share of voice", "counter-messaging". Do NOT use for business signals like funding/hiring (use competitor-intel), single-company deep dives (use company-deep-dive), or meeting prep (use meeting-prep).
What it loads into context
Frontmatter
321 tokensAlways available to the agent
SKILL.md
3,959 tokensWhen the skill is activated
Reference documents
18,551 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Agent Teams Mode (Dual-Mode)
- Error Handling
Files
SKILL.mdcore17,184 bytesSKILL.mdcore17,184 bytesSKILL.mdcore17,184 bytesSKILL.mdcore17,184 bytesSKILL.mdcore17,184 bytesSKILL.mdcore17,184 bytesSKILL.mdcore17,184 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/positioning-agent-prompt.mddoc5,903 bytesreferences/positioning-snapshot-format.mddoc1,719 bytesreferences/profile-and-onboarding.mddoc9,344 bytes
Read SKILL.md
# Competitor Positioning
Marketing-focused competitive positioning analysis powered by Nimble's web data APIs.
Built for marketing teams who need to understand how competitors present themselves —
messaging, value props, content themes, pricing — and how that evolves over time.
The output is a **marketing briefing**, not a signal feed. Every insight should answer:
"what does this mean for our messaging and positioning?"
User request: $ARGUMENTS
**Argument parsing** — determine what to do before running anything:
- No arguments → run full workflow (scope confirmation in Step 2)
- Competitor names (e.g., "Exa, Tavily") → research only those, skip scope confirmationView the complete source on GitHubcredit-risk
When your agent uses it
Builds a dated, sourced credit picture of a company: financials, ratings, debt events, payment behaviour, distress signals and ownership, with a risk call and its reasons, using the Nimble `credit-risk` agent template on live web data. Use when the user says "credit risk of", "counterparty check", "can they pay", "is this supplier at risk", "credit picture for", "distress signals", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use for a compliance screen (use kyc-screening) or an investment memo (use due-diligence).
What it loads into context
Frontmatter
496 tokensAlways available to the agent
SKILL.md
2,150 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Files
SKILL.mdcore8,422 bytesSKILL.mdcore8,422 bytesSKILL.mdcore8,422 bytes
Read SKILL.md
# Credit risk
Builds a dated, sourced credit picture of a company: financials, ratings, debt events, payment behaviour, distress signals and ownership, with a risk call and its reasons.
User request: $ARGUMENTS
## What the user gets
Financials with periods, ratings, debt events, payment behaviour, distress signals, ownership, and a risk call (low, moderate, elevated or high) with the reasons behind it.
## Agent template
This skill runs the Nimble gallery template `credit-risk`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHubdeal-sourcing
When your agent uses it
Builds a list of private companies that fit an investment thesis (sector, geography, size, ownership), with evidence for each criterion, using the Nimble `deal-sourcing` agent template on live web data. Use when the user says "find acquisition targets", "deal sourcing", "map the market for", "founder-owned companies in", "off-market targets", "companies that fit our thesis", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use for sales prospect lists (use account-discovery) or to research one company (use due-diligence).
What it loads into context
Frontmatter
493 tokensAlways available to the agent
SKILL.md
2,168 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Files
SKILL.mdcore8,476 bytesSKILL.mdcore8,476 bytesSKILL.mdcore8,476 bytes
Read SKILL.md
# Deal sourcing
Builds a list of private companies that fit an investment thesis (sector, geography, size, ownership), with evidence for each criterion.
User request: $ARGUMENTS
## What the user gets
A list of companies that fit the thesis, with ownership and evidence for each criterion. A short list is an honest answer.
## Agent template
This skill runs the Nimble gallery template `deal-sourcing`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHubdecision-maker-identification
When your agent uses it
Finds the people who hold given roles at a company today, with current title, career history and the source that proves it, using the Nimble `decision-maker-identification` agent template on live web data. Use when the user says "who is the CFO at", "find the head of X at", "find the buying committee", "decision makers at", "who runs RevOps at", "find contacts at", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use to fill company-level fields (use account-enrichment). It never returns emails or phone numbers.
What it loads into context
Frontmatter
494 tokensAlways available to the agent
SKILL.md
2,217 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Files
SKILL.mdcore8,647 bytesSKILL.mdcore8,647 bytesSKILL.mdcore8,647 bytesSKILL.mdcore8,647 bytesSKILL.mdcore8,647 bytesSKILL.mdcore8,647 bytes
Read SKILL.md
# Decision-maker identification
Finds the people who hold given roles at a company today, with current title, career history and the source that proves it.
User request: $ARGUMENTS
## What the user gets
For each role, the person who holds it now: name, exact title, start date, previous roles, public profiles and a dated source. Roles it cannot confirm are listed as missing.
## Agent template
This skill runs the Nimble gallery template `decision-maker-identification`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHubdue-diligence
When your agent uses it
Writes a first-pass due diligence memo on a private company: business, traction, team, funding, financial signals, legal issues, reputation and red flags, every claim dated and cited, using the Nimble `due-diligence` agent template on live web data. Use when the user says "due diligence on", "DD memo", "investment memo on", "diligence this company", "red flags for", "should we invest in", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use for a sales meeting brief (use account-brief) or a credit view (use credit-risk).
What it loads into context
Frontmatter
503 tokensAlways available to the agent
SKILL.md
2,150 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Files
SKILL.mdcore8,335 bytesSKILL.mdcore8,335 bytesSKILL.mdcore8,335 bytesSKILL.mdcore8,335 bytes
Read SKILL.md
# Due diligence
Writes a first-pass due diligence memo on a private company: business, traction, team, funding, financial signals, legal issues, reputation and red flags, every claim dated and cited.
User request: $ARGUMENTS
## What the user gets
A memo with sections for business, traction, team, funding, financial signals, legal and regulatory, reputation, red flags and a short verdict. Every claim has a date and source.
## Agent template
This skill runs the Nimble gallery template `due-diligence`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHubhealthcare-providers-enrich
When your agent uses it
Fills gaps in existing healthcare practitioner lists — adds missing phone numbers, credentials, specialties, contact info, education, reviews, and regulatory data. Triggers: "enrich my provider list", "fill in missing data", "add phone numbers to these doctors", "complete this practitioner database", "enrich CRM export", "fill gaps in my provider data", "supplement this healthcare list". Accepts CSV, Google Sheet URL, or pasted data. Searches for each provider's practice website, extracts missing fields, and enriches with reviews, clinical trials, and accreditation via WSAs. Do NOT use for extracting providers from practice URLs — use healthcare-providers-extract instead. Do NOT use for validating credentials — use healthcare-providers-verify instead. Do NOT use for discovering practices — use market-finder or local-places instead. Do NOT use for general extraction — use nimble-web-expert instead.
What it loads into context
Frontmatter
329 tokensAlways available to the agent
SKILL.md
3,665 tokensWhen the skill is activated
Reference documents
19,939 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Sub-Agent Strategy
- Error Handling
Files
SKILL.mdcore15,324 bytesSKILL.mdcore15,324 bytesSKILL.mdcore15,324 bytesSKILL.mdcore15,324 bytesSKILL.mdcore15,324 bytesSKILL.mdcore15,324 bytesSKILL.mdcore15,324 bytesSKILL.mdcore15,324 bytesSKILL.mdcore15,324 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytesreferences/provider-extraction-patterns.mddoc6,868 bytesreferences/wsa-reference.mddoc6,385 bytes
Read SKILL.md
# Healthcare Providers Enrich
Fill gaps in existing practitioner lists with verified web data, powered by Nimble's
web data APIs.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
---
## Instructions
View the complete source on GitHubhealthcare-providers-extract
When your agent uses it
Extracts structured practitioner data from healthcare practice websites. Returns names, credentials, specialties, contact info, and education for every provider on a practice's site. Use when user asks to extract, pull, or list doctors, providers, or staff from practice websites. Triggers: "extract doctors from", "pull providers from", "who are the providers at", "build a provider database", "list all doctors at", "scrape the team page", "get practitioner data from". Accepts practice URLs (pasted, CSV, Google Sheet) or discovers practices via Google Maps when given specialty + location. Single sites or 100+ URLs. Do NOT use for filling data gaps — use healthcare-providers-enrich instead. Do NOT use for credential validation — use healthcare-providers-verify instead. Do NOT use for discovering practices — use market-finder or local-places instead. Do NOT use for general extraction — use nimble-web-expert instead.
What it loads into context
Frontmatter
341 tokensAlways available to the agent
SKILL.md
3,332 tokensWhen the skill is activated
Reference documents
20,146 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Sub-Agent Strategy
- Error Handling
Files
SKILL.mdcore13,903 bytesSKILL.mdcore13,903 bytesSKILL.mdcore13,903 bytesSKILL.mdcore13,903 bytesSKILL.mdcore13,903 bytesSKILL.mdcore13,903 bytesSKILL.mdcore13,903 bytesSKILL.mdcore13,903 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytesreferences/provider-extraction-patterns.mddoc6,868 bytesreferences/wsa-reference.mddoc7,457 bytes
Read SKILL.md
# Healthcare Providers Extract
Structured practitioner extraction from healthcare practice websites, powered by
Nimble's web data APIs.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
---
## Instructions
View the complete source on GitHubhealthcare-providers-verify
When your agent uses it
Validates practitioner credentials and license status against the NPI registry. Cross-references specialties, credentials, and practice addresses against official records. Returns Verified / Partially Verified / Unverified / Flagged per practitioner with mismatch details and source URLs. Triggers: "verify these doctors", "check provider credentials", "validate licenses", "verify NPI numbers", "cross-check credentials against NPI", "compliance audit on providers", "are these practitioners still licensed", "validate my provider list". Accepts CSV, Google Sheet URL, or pasted data. Do NOT use for extracting providers from practice URLs — use healthcare-providers-extract instead. Do NOT use for filling data gaps — use healthcare-providers-enrich instead. Do NOT use for discovering practices — use market-finder or local-places instead. Do NOT use for general extraction — use nimble-web-expert instead.
What it loads into context
Frontmatter
322 tokensAlways available to the agent
SKILL.md
4,351 tokensWhen the skill is activated
Reference documents
22,179 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Sub-Agent Strategy
- Error Handling
Files
SKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesSKILL.mdcore18,043 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/npi-verification-patterns.mddoc10,201 bytesreferences/profile-and-onboarding.mddoc9,344 bytesreferences/provider-extraction-patterns.mddoc6,868 bytesreferences/wsa-reference.mddoc6,238 bytes
Read SKILL.md
# Healthcare Providers Verify
Validate practitioner credentials against the NPI registry and authoritative
sources, powered by Nimble's web data APIs.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
---
## Instructions
View the complete source on GitHubkyc-screening
When your agent uses it
Runs a sourced KYC / AML research screen on a company: registration, officers, beneficial owners, sanctions, PEPs and adverse media, with namesakes excluded and a risk rating, using the Nimble `kyc-screening` agent template on live web data. Use when the user says "KYC on", "KYB", "AML screen", "sanctions check", "beneficial owners of", "screen this company", "onboarding check", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use for a credit view (use credit-risk). Not a certified compliance check.
What it loads into context
Frontmatter
499 tokensAlways available to the agent
SKILL.md
2,160 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Files
SKILL.mdcore8,362 bytesSKILL.mdcore8,362 bytesSKILL.mdcore8,362 bytes
Read SKILL.md
# KYC screening
Runs a sourced KYC / AML research screen on a company: registration, officers, beneficial owners, sanctions, PEPs and adverse media, with namesakes excluded and a risk rating.
User request: $ARGUMENTS
## What the user gets
Registry details, officers and owners, sanctions and PEP checks, adverse media, related entities, how many namesakes were excluded, and a risk rating with reasons.
## Agent template
This skill runs the Nimble gallery template `kyc-screening`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHublaunch-monitor
When your agent uses it
Monitors press, social, developer communities, and competitor channels from any point around a product launch — tracking sentiment, flagging mischaracterizations, surfacing competitor responses, and recommending actions in real time. Covers press, Reddit, LinkedIn, JavaScript-heavy pages, and live community forums, triaging every signal by urgency. Delivers a Response War Room dashboard with a live signal feed, mischaracterization tracker, competitor response panel, and sentiment velocity chart. Use when asked to "monitor this launch", "track the launch", "what's being said about the launch", "flag any mischaracterizations", "competitor response to the launch", "post-launch coverage", "check press coverage for the launch", or "what's the reaction to the announcement". Do NOT use for ongoing brand monitoring unrelated to a launch — use brand-mention-monitor instead. Do NOT use for ongoing competitor intelligence unrelated to a specific launch window — use competitor-intel instead.
What it loads into context
Frontmatter
335 tokensAlways available to the agent
SKILL.md
5,917 tokensWhen the skill is activated
Reference documents
19,619 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Onboarding message
- Preflight
- How to start
- Step 0 — Context profiling (run before any searches)
- Step 1 — Signal sweep
- Step 2 — Signal triage
- Step 3 — Mischaracterization analysis
- Step 4 — Sentiment velocity
- Memory dedup (filter already-known signals)
- Output template (REQUIRED)
- Saved preferences
- Distribution
- Re-run behavior
- Related skills — next steps
- Materiality threshold
Files
SKILL.mdcore25,387 bytesSKILL.mdcore25,387 bytesSKILL.mdcore25,387 bytesSKILL.mdcore25,387 bytesSKILL.mdcore25,387 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytesreferences/sources.mddoc12,099 bytesreferences/template.htmlasset28,659 bytes
Read SKILL.md
# Launch Monitor
Monitors press, social, and community forums from launch day — tracking sentiment, flagging mischaracterizations, surfacing competitor responses, and recommending actions so you can respond fast.
---
## Onboarding message
When this skill is triggered for the first time in a session, send this message. Send it exactly once per session, before asking any setup questions. Do not skip it even when the user's opening message already names a product — the onboarding sets expectations for what the skill collects and how it works.
> 👋 **Launch Monitor is ready.**
>
> This skill monitors press, social media, developer communities, and competitor channels around a product launch — tracking sentiment, flagging mischaracterizations, surfacing competitor responses, and telling you exactly what to respond to and how.
>View the complete source on GitHublocal-places
When your agent uses it
Discovers, enriches, and scores local businesses in any neighborhood using Nimble Web Search Agents (WSAs) and web data. Returns a structured, ranked list with confidence scores, reviews, social presence, and an interactive map. Use this skill when the user asks about local businesses, places, or neighborhood discovery. Common triggers: "find all coffee shops in", "map every bar in", "local businesses in", "discover gyms near", "what restaurants are in", "neighborhood guide for", "local places in", "find places near", "list all [business type] in [area]", "best [type] near [location]", "build a neighborhood guide", "local place search". Requires the Nimble CLI (nimble extract:templates run, nimble search, nimble extract) for live web data via WSAs and fallback search. Do NOT use for competitor analysis or monitoring (use competitor-intel), company research or deep dives (use company-deep-dive), general web search or extraction (use nimble-web-expert).
What it loads into context
Frontmatter
360 tokensAlways available to the agent
SKILL.md
4,274 tokensWhen the skill is activated
Reference documents
18,438 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Sub-Agent Strategy
- Agent Teams Mode (Dual-Mode)
- Error Handling
Files
SKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesSKILL.mdcore16,930 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytesreferences/wsa-pipeline.mddoc7,193 bytes
Read SKILL.md
# Local Places
Location intelligence powered by Nimble Web Search Agents and web data APIs.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
---
## Instructions
### Step 0: PreflightView the complete source on GitHubmarket-finder
When your agent uses it
Discovers all businesses of a given type in any geography using Nimble WSAs. Two modes: Discovery finds businesses from scratch; Audit compares a user's existing list (Google Sheet, CSV, inline) against fresh discovery, categorizing entries as matched, discovered-only, or reference-only. Vertical presets (Healthcare, SaaS, Restaurants, Legal, Auto/Home) auto-select WSA routing. Triggers: "find all X in Y", "build a list of", "market sizing", "account universe", "how many X in Y", "TAM for", "discover all", "audit my list", "compare against", "what am I missing", "gap analysis", "verify my business list", "prospect list". Do NOT use for competitor monitoring — use competitor-intel instead. Do NOT use for company deep dives — use company-deep-dive instead. Do NOT use for neighborhood-level exploration with social enrichment — use local-places instead.
What it loads into context
Frontmatter
336 tokensAlways available to the agent
SKILL.md
4,691 tokensWhen the skill is activated
Reference documents
20,146 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Sub-Agent Strategy
- Agent Teams Mode (Dual-Mode)
- Error Handling
Files
SKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesSKILL.mdcore19,053 bytesreferences/audit-mode.mddoc7,611 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytesreferences/vertical-presets.mddoc6,513 bytes
Read SKILL.md
# Market Finder
Market intelligence powered by Nimble Web Search Agents.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
---
## Instructions
### Step 0: PreflightView the complete source on GitHubmeeting-prep
When your agent uses it
Researches meeting attendees and their companies before any meeting using real-time web data. Surfaces roles, recent activity, company context, and talking points — then maps cross-attendee relationships. Use this skill when the user asks to prepare for a meeting, research someone they're meeting, or wants context on attendees. Common triggers: "prepare me for my meeting", "who am I meeting with", "research this person", "meeting prep", "brief me on [person]", "I have a meeting with [person/company]", "get me ready for my call", "what should I know about [person]", "background on [person] before our meeting", "attendee research". Requires the Nimble CLI (nimble search, nimble extract) for live web data. Do NOT use for multi-company competitor monitoring (use competitor-intel) or single-company deep dives without attendees (use company-deep-dive).
What it loads into context
Frontmatter
322 tokensAlways available to the agent
SKILL.md
5,626 tokensWhen the skill is activated
Reference documents
17,805 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Agent Teams Mode (Dual-Mode)
- What This Skill Is NOT
- Error Handling
Files
SKILL.mdcore24,374 bytesSKILL.mdcore24,374 bytesSKILL.mdcore24,374 bytesSKILL.mdcore24,374 bytesSKILL.mdcore24,374 bytesreferences/attendee-agent-prompt.mddoc4,545 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytes
Read SKILL.md
# Meeting Prep
Research-powered meeting preparation with attendee intelligence and company context.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
---
## Instructions
### Step 0: PreflightView the complete source on GitHubnimble-databricks-data-products
When your agent uses it
Builds Databricks data products from live web data, end to end: discovers the right Nimble web-data agents, scrapes into Delta tables, and produces an AI/BI dashboard and/or a deployed Databricks App — a table → dashboard → app workflow, for production data products or quick demos. Use whenever a request pairs live or scraped web data WITH a Databricks destination — e.g. "scrape Amazon/Walmart prices into a Delta table and build a dashboard", "load Zillow/Instagram/Maps/search results into Databricks and build a dashboard or app", "showcase Nimble + Databricks to a prospect". Prefer it over nimble-web-expert or competitor-intel when the data lands in Databricks. Do NOT use for one-off web fetches or CSV exports with no Databricks destination — use nimble-web-expert instead. Do NOT use for competitor or company research briefings — use competitor-intel or company-deep-dive instead. Do NOT use for generic Databricks work with no Nimble/web-data angle — use the official databricks-* skills instead.
What it loads into context
Frontmatter
348 tokensAlways available to the agent
SKILL.md
2,546 tokensWhen the skill is activated
Reference documents
8,578 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Golden rules
- Workflow
- Reference map
Scripts executed separately
scripts/build_dashboard.pyscripts/ingest.sh
Files
SKILL.mdcore10,395 bytesSKILL.mdcore10,395 bytesSKILL.mdcore10,395 bytesSKILL.mdcore10,395 bytesSKILL.mdcore10,395 bytesSKILL.mdcore10,395 bytesSKILL.mdcore10,395 bytesSKILL.mdcore10,395 bytesSKILL.mdcore10,395 bytesassets/nimble-logo.pngasset25,427 bytesreferences/app-cookbook.mddoc4,795 bytesreferences/branding.mddoc2,447 bytesreferences/dashboard-cookbook.mddoc5,919 bytesreferences/databricks-skills.mddoc1,944 bytesreferences/install-nimble-integration.mddoc2,544 bytesreferences/nimble-agents.mddoc11,840 bytesreferences/preflight.mddoc3,425 bytesscripts/build_dashboard.pyruns13,611 bytesscripts/ingest.shruns2,390 bytes
Read SKILL.md
# Nimble on Databricks — data products builder
Turn a natural-language brief like
`pricing analysis on dog products from walmart and amazon` into working Databricks data products:
**discover agents → ingest live web search data into Delta → build dashboard and/or app → deliver links.**
Equally at home for a quick demo or a real, reusable data product.
You are the orchestrator. Databricks mechanics are delegated to the official `databricks-*`
skills (see `references/databricks-skills.md`); this skill owns the **Nimble glue and the gaps**
(agent discovery, ingestion-from-agents, the AI/BI dashboard JSON, branding).
## Golden rules
- **Discover, don't assume.** Read agent names via `nimble_agent_list()`, input params viaView the complete source on GitHubnimble-web-expert
When your agent uses it
Get web data now — fast, incremental, immediately responsive to what the user needs. The only way Claude can access live websites. USE FOR: - Fetching any URL or reading any webpage - Scraping prices, listings, reviews, jobs, stats, docs from any site - Running Extraction Templates — reusable, site-specific structured scrapers - Running Web Search Agents — open-ended research, enrichment, and dataset building with citations - Discovering URLs on a site before bulk extraction - Calling public REST/XHR API endpoints - Web search and research (8 focus modes) - Bulk crawling website sections Must be pre-installed and authenticated. Run `nimble --version` to verify (>= 1.2.0).
What it loads into context
Frontmatter
754 tokensAlways available to the agent
SKILL.md
5,428 tokensWhen the skill is activated
Reference documents
36,206 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core principles
- Capabilities
- Interactive UX
- Prerequisites
- Analyze & Route
- Workflow
- Response shapes
- Output & Organization
- Self-Improvement
- Guardrails
- Reference files
Files
README.mddoc4,574 bytesSKILL.mdcore24,279 bytesSKILL.mdcore24,279 bytesSKILL.mdcore24,279 bytesSKILL.mdcore24,279 bytesSKILL.mdcore24,279 bytesSKILL.mdcore24,279 bytesSKILL.mdcore24,279 bytesSKILL.mdcore24,279 bytesreferences/batch-patterns.mddoc10,912 bytesreferences/error-handling.mddoc8,199 bytesreferences/nimble-agents/reference.mddoc21,365 bytesreferences/nimble-crawl/reference.mddoc7,011 bytesreferences/nimble-extract-templates/reference.mddoc6,389 bytesreferences/nimble-extract/browser-actions.mddoc10,910 bytesreferences/nimble-extract/browser-investigation.mddoc6,665 bytesreferences/nimble-extract/network-capture.mddoc8,487 bytesreferences/nimble-extract/parsing-schema.mddoc10,283 bytesreferences/nimble-extract/reference.mddoc15,979 bytesreferences/nimble-map/reference.mddoc3,967 bytesreferences/nimble-search/reference.mddoc8,479 bytesreferences/nimble-search/search-focus-modes.mddoc6,626 bytesreferences/nimble-tasks/reference.mddoc7,096 bytesreferences/recipes.mddoc6,906 bytesrules/nimble-web-expert.mdcasset3,827 bytesrules/output.mddoc1,123 bytesrules/setup.mddoc6,591 bytes
Read SKILL.md
# Nimble Web Expert
Web extraction, search, and URL discovery using the Nimble CLI. Returns clean structured data from any website.
User request: $ARGUMENTS
## Core principles
- **Route by intent first** (see [Analyze & Route](#analyze--route) for the full decision model). Named site with a matching Extraction Template + a direct item to look up → run the template. Site with no template, or a need that requires discovery/reasoning across pages → a Web Search Agent. One-off single URL → `nimble extract`. Raw results to work from ("find pages/articles about…") → `nimble search`; a synthesized deliverable (report, brief, comparison, recommendation) → a Web Search Agent. Discover/crawl URLs → `nimble map` or `nimble crawl`.
- **Web Search Agent runs: pick a run mode before building the command.** Default to named create-or-reuse — `nimble agents run --agent-name <stable-name>` — so a repeat session lands on the same agent. `agents:runs create` is the explicit-agent-ID route only and requires `--agent-id`. `references/nimble-agents/reference.md` has the mode table, `use_case` locking, and the one-time `skill` override.
- **One command → present results → done.** Run once, show the data immediately as a table. Do NOT experiment, loop, or write Python to parse output.
- **Multiple inputs → always parallel.** 2+ URLs/keywords/ASINs → `&`+`wait`. 6–20 → `xargs -P`. 20+ → Python asyncio script. See `references/batch-patterns.md`.
- **Escalate render tiers silently on empty or truncated content.** Tier 1 → 2 → 3 → … without asking. Surface a decision only when all tiers fail and investigation tools are needed. An access barrier is a different outcome, not a tier to climb — see Guardrails.
- **Never answer from training data.** Live prices, current news, today's listings → always fetch via Nimble. If unavailable, say so.View the complete source on GitHubportfolio-monitoring
When your agent uses it
Lists material events at a holding since a date: exec changes, litigation, rating actions, guidance and defaults, with why each one matters, using the Nimble `portfolio-monitoring` agent template on live web data. Use when the user says "what happened at [holding]", "monitor my portfolio", "material events", "check my holdings since", "portfolio news", or arrives from a Nimble use-case page. Interviews the user for the inputs, shows quick search results first, then runs the template at medium and high effort and shows each result as it arrives. Do NOT use for sales accounts (use account-signals) or a full credit view (use credit-risk).
What it loads into context
Frontmatter
486 tokensAlways available to the agent
SKILL.md
2,147 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What the user gets
- Agent template
- Flow
- Using Nimble well
- Pitfalls
- Rules
Files
SKILL.mdcore8,390 bytesSKILL.mdcore8,390 bytesSKILL.mdcore8,390 bytes
Read SKILL.md
# Portfolio monitoring
Lists material events at a holding since a date: exec changes, litigation, rating actions, guidance and defaults, with why each one matters.
User request: $ARGUMENTS
## What the user gets
Only material events after the since date, each dated and cited, with why it matters. If nothing material happened, an empty list and the sources it checked.
## Agent template
This skill runs the Nimble gallery template `portfolio-monitoring`. The agent's instructions, sources and output schema live in the template. Do not rewrite them in the run.
View the complete source on GitHubseo-intel
When your agent uses it
SEO intelligence toolkit covering the full lifecycle via live web data: keyword research, rank tracking, site audits, content gap analysis, competitor keyword reverse-engineering, AI visibility across five platforms (ChatGPT, Perplexity, Google AI, Gemini, Grok), and GitHub repo SEO. Crawls real sites and SERPs via Nimble CLI — no fabricated metrics. Triggers: "SEO", "keywords", "rank tracker", "site audit", "content gap", "competitor keywords", "AI visibility", "GitHub SEO", "SERP analysis", "keyword research", "technical SEO", "keyword difficulty", "topic clusters", "ranking delta", "on-page SEO", "AI citation audit". Do NOT use for competitor business signals — use `competitor-intel` instead. Do NOT use for competitor messaging — use `competitor-positioning` instead. Do NOT use for general web scraping — use `nimble-web-expert` instead.
What it loads into context
Frontmatter
340 tokensAlways available to the agent
SKILL.md
1,259 tokensWhen the skill is activated
Reference documents
65,088 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Workflow Router
Files
SKILL.mdcore5,285 bytesSKILL.mdcore5,285 bytesreferences/ai-platform-profiles.mddoc11,542 bytesreferences/ai-visibility-agent-prompt.mddoc6,300 bytesreferences/audit-agent-prompt.mddoc3,884 bytesreferences/content-gap-agent-prompt.mddoc5,783 bytesreferences/github-seo-checks.mddoc12,044 bytesreferences/keyword-research-agent-prompt.mddoc2,990 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytesreferences/seo-audit-checks.mddoc15,437 bytesreferences/seo-extraction-prompt.mddoc6,923 bytesreferences/serp-query-patterns.mddoc6,551 bytesreferences/wf-ai-visibility.mddoc20,160 bytesreferences/wf-competitor-keywords.mddoc19,283 bytesreferences/wf-content-gap.mddoc18,407 bytesreferences/wf-github-seo.mddoc16,088 bytesreferences/wf-keyword-research.mddoc18,701 bytesreferences/wf-rank-tracker.mddoc15,237 bytesreferences/wf-site-audit.mddoc15,167 bytes
Read SKILL.md
# SEO Intelligence Toolkit
All-in-one SEO intelligence: keyword discovery, rank tracking, technical audits,
content gaps, competitor analysis, AI visibility, and GitHub SEO.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
Tag all `nimble` CLI calls: `nimble --client-source nimble-agent-skills <subcommand>`. MCP requests are attributed at the transport level — see `references/nimble-playbook.md`.
---
## Workflow RouterView the complete source on GitHubtalent-sourcing
When your agent uses it
Finds qualified candidates for a role by searching LinkedIn, Indeed, GitHub, and other professional platforms using Nimble Web Search Agents. Accepts a job description, role title, or freeform request and returns a ranked candidate list with profiles, skills, and contact signals. Use this skill when the user wants to find, source, or recruit candidates for a role. Common triggers: "find candidates for", "source engineers in", "who can I hire for", "find me a [role]", "recruiting for", "talent search", "find a [role] in [city]", "build a candidate list", "sourcing for [role]", "who's available for", "find potential hires". Also triggers on a pasted job description followed by a sourcing request. Do NOT use for job market research or salary benchmarking — use market-finder instead. Do NOT use for researching a single known person — use company-deep-dive or meeting-prep instead.
What it loads into context
Frontmatter
340 tokensAlways available to the agent
SKILL.md
2,765 tokensWhen the skill is activated
Reference documents
16,722 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Instructions
- Error Handling
Files
SKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesSKILL.mdcore10,960 bytesreferences/memory-and-distribution.mddoc22,058 bytesreferences/nimble-playbook.mddoc37,015 bytesreferences/profile-and-onboarding.mddoc9,344 bytes
Read SKILL.md
# Talent Sourcing
Candidate discovery powered by Nimble Web Search Agents.
User request: $ARGUMENTS
**Before running any commands**, read `references/nimble-playbook.md` for Claude Code
constraints (no shell state, no `&`/`wait`, sub-agent permissions, communication style).
---
## Instructions
### Step 0: PreflightView the complete source on GitHubSkills included
- account-brief
- account-discovery
- account-enrichment
- account-signals
- brand-mention-monitor
- company-deep-dive
- competitor-intel
- competitor-positioning
- credit-risk
- deal-sourcing
- decision-maker-identification
- due-diligence
- healthcare-providers-enrich
- healthcare-providers-extract
- healthcare-providers-verify
- kyc-screening
- launch-monitor
- local-places
- market-finder
- meeting-prep
- nimble-databricks-data-products
- nimble-web-expert
- portfolio-monitoring
- seo-intel
- talent-sourcing
Repository facts
- License
- MIT
- Created
- Jan 29, 2026
- Last pushed
- Oct 29, 2026
- Forks
- 19
- Open issues
- 0
- Project activity
- Active
Before you install
Network or broad shellAutomated signals, not a guarantee
Checked Nov 6, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 156 notes
agents/nimble-analyst.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/account-brief/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/account-brief/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/example.html:335Analysis incomplete: physical or joined line exceeds character limitskills/account-discovery/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/account-discovery/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/account-enrichment/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/account-enrichment/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/account-signals/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/account-signals/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/brand-mention-monitor/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- 49 broad permissionsin 25 files: skills/account-discovery/SKILL.md:1 skills/account-enrichment/SKILL.md:1 skills/account-signals/SKILL.md:1 and 22 more
- 2 dangerous shell commandsin 1 file: skills/nimble-databricks-data-products/scripts/ingest.sh:23
- 1,860 network referencesin 94 files: skills/nimble-web-expert/references/nimble-extract/reference.md:68 skills/nimble-web-expert/references/nimble-extract/browser-actions.md:13 skills/brand-mention-monitor/example.html:331 and 91 more
- No hidden or obfuscated text
- No instruction overrides
- 4 executable scriptsin 2 files: skills/nimble-databricks-data-products/scripts/build_dashboard.py:1 skills/nimble-databricks-data-products/scripts/ingest.sh:1
- 176 references to secretsin 38 files: skills/nimble-web-expert/rules/setup.md:96 skills/brand-mention-monitor/references/nimble-playbook.md:28 skills/company-deep-dive/references/nimble-playbook.md:28 and 35 more
- No requests to vote in Hot
Show all 2,091 signals by file
.claude-plugin/plugin.json
- Network accessline 6
"name": "Nimble", "email": "support@nimbleway.com", "url": "https://www.nimbleway.com" - Network accessline 7
"email": "support@nimbleway.com", "url": "https://www.nimbleway.com" }, - Network accessline 8
"url": "https://www.nimbleway.com" - Network accessline 9
}, "homepage": "https://www.nimbleway.com", "repository": "https://github.com/Nimbleway/agent-skills", - Network accessline 10
"homepage": "https://www.nimbleway.com", - Network accessline 11
"repository": "https://github.com/Nimbleway/agent-skills",
skills/account-brief/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Network accessline 74
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 131
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 132
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 138
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/account-discovery/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Broad permissionsline 1
Bash(npm --version) - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 130
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 130
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 137
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc - Network accessline 137
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/account-enrichment/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Broad permissionsline 1
Bash(npm --version) - Network accessline 74
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 74
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 132
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 132
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 133
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 133
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 139
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc - Network accessline 139
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/account-signals/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Broad permissionsline 1
Bash(npm --version) - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 131
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 132
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 132
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 138
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc - Network accessline 138
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/brand-mention-monitor/SKILL.md
- Broad permissionsline 1
Bash(python3:*) - Broad permissionsline 1
Bash(python3:*) - Network accessline 344
**Source URL rule:** Every mention must include `<a href="[EXACT_NIMBLE_URL]" class="src-link">↗ source</a>` with the exact article/post URL from Nimble. Never use a homepage. - CORRECT: `https://reddit.com/r/SaaS/comments/abc123/title` - Network accessline 344
**Source URL rule:** Every mention must include `<a href="[EXACT_NIMBLE_URL]" class="src-link">↗ source</a>` with the exact article/post URL from Nimble. Never use a homepage. - CORRECT: `https://reddit.com/r/SaaS/comments/abc123/title` - Network accessline 345
Every mention must include `<a href="[EXACT_NIMBLE_URL]" class="src-link">↗ source</a>` with the exact article/post URL from Nimble. Never use a homepage. - CORRECT: `https://reddit.com/r/SaaS/comments/abc123/title` - CORRECT: `https://x.co - Network accessline 345
Every mention must include `<a href="[EXACT_NIMBLE_URL]" class="src-link">↗ source</a>` with the exact article/post URL from Nimble. Never use a homepage. - CORRECT: `https://reddit.com/r/SaaS/comments/abc123/title` - CORRECT: `https://x.co - Network accessline 346
- CORRECT: `https://reddit.com/r/SaaS/comments/abc123/title` - Network accessline 346
- CORRECT: `https://reddit.com/r/SaaS/comments/abc123/title` - Network accessline 347
- CORRECT: `https://x.com/username/status/1234567890` - Network accessline 347
- CORRECT: `https://x.com/username/status/1234567890` - Network accessline 348
- WRONG: `https://reddit.com` WRONG: `https://x.com` - Network accessline 348
- WRONG: `https://reddit.com` WRONG: `https://x.com` - Network accessline 388
Every mention must include the exact Nimble result URL. **CORRECT:** `https://reddit.com/r/SaaS/comments/abc123/title` - Network accessline 388
Every mention must include the exact Nimble result URL. **CORRECT:** `https://reddit.com/r/SaaS/comments/abc123/title` - Network accessline 389
**CORRECT:** `https://reddit.com/r/SaaS/comments/abc123/title` - Network accessline 389
**CORRECT:** `https://reddit.com/r/SaaS/comments/abc123/title` - Network accessline 390
**WRONG:** `https://reddit.com` - Network accessline 390
**WRONG:** `https://reddit.com`
skills/brand-mention-monitor/example.html
- Network accessline 331
<script src="https://cdnjs.cloudflare.com/ajax/libs/d3/7.8.5/d3.min.js"></script> - Network accessline 331
<script src="https://cdnjs.cloudflare.com/ajax/libs/d3/7.8.5/d3.min.js"></script> - Network accessline 332
<script src="https://cdnjs.cloudflare.com/ajax/libs/topojson/3.0.2/topojson.min.js"></script> - Network accessline 332
<script src="https://cdnjs.cloudflare.com/ajax/libs/topojson/3.0.2/topojson.min.js"></script> - Network accessline 333
<script> const mentions = [ {reach:95,velocity:88,sentiment:68,riskTopic:90,opp:8,tier:'crisis',velDir:'up',platform:'news',head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"',quote:'"Within days of its releas - Network accessline 333
<script> const mentions = [ {reach:95,velocity:88,sentiment:68,riskTopic:90,opp:8,tier:'crisis',velDir:'up',platform:'news',head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"',quote:'"Within days of its releas - Network accessline 334
const mentions = [ {reach:95,velocity:88,sentiment:68,riskTopic:90,opp:8,tier:'crisis',velDir:'up',platform:'news',head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"',quote:'"Within days of its release, Anthro - Network accessline 334
const mentions = [ {reach:95,velocity:88,sentiment:68,riskTopic:90,opp:8,tier:'crisis',velDir:'up',platform:'news',head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"',quote:'"Within days of its release, Anthro - Network accessline 335
{reach:95,velocity:88,sentiment:68,riskTopic:90,opp:8,tier:'crisis',velDir:'up',platform:'news',head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"',quote:'"Within days of its release, Anthropic\u2019s most sophi - Network accessline 335
{reach:95,velocity:88,sentiment:68,riskTopic:90,opp:8,tier:'crisis',velDir:'up',platform:'news',head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"',quote:'"Within days of its release, Anthropic\u2019s most sophi - Network accessline 336
{reach:90,velocity:80,sentiment:62,riskTopic:88,opp:6,tier:'crisis',velDir:'up',platform:'news',head:'PBS NewsHour: Anthropic disables new AI model after White House security directive',quote:'"The Trump administration forced Anthropic, one - Network accessline 336
{reach:90,velocity:80,sentiment:62,riskTopic:88,opp:6,tier:'crisis',velDir:'up',platform:'news',head:'PBS NewsHour: Anthropic disables new AI model after White House security directive',quote:'"The Trump administration forced Anthropic, one - Network accessline 337
{reach:88,velocity:72,sentiment:78,riskTopic:82,opp:5,tier:'crisis',velDir:'up',platform:'news',head:'WSJ: "Anthropic Sued Over Limits on Its $200-a-Month AI Plans"',quote:'"Federal lawsuit alleges the company oversold usage allowances on i - Network accessline 337
{reach:88,velocity:72,sentiment:78,riskTopic:82,opp:5,tier:'crisis',velDir:'up',platform:'news',head:'WSJ: "Anthropic Sued Over Limits on Its $200-a-Month AI Plans"',quote:'"Federal lawsuit alleges the company oversold usage allowances on i - Network accessline 338
{reach:72,velocity:58,sentiment:70,riskTopic:45,opp:12,tier:'watch',velDir:'up',platform:'x',head:'Widely-shared essay: "Anthropic is losing the mandate of heaven"',quote:'"When Anthropic banned the ability to use Claude Code inside other h - Network accessline 338
{reach:72,velocity:58,sentiment:70,riskTopic:45,opp:12,tier:'watch',velDir:'up',platform:'x',head:'Widely-shared essay: "Anthropic is losing the mandate of heaven"',quote:'"When Anthropic banned the ability to use Claude Code inside other h - Network accessline 339
{reach:65,velocity:50,sentiment:62,riskTopic:35,opp:10,tier:'watch',velDir:'flat',platform:'reddit',head:'r/ClaudeAI: backlash to Anthropic rolling out identity verification',quote:'"I do like Anthropic\u2019s offerings but DS, MiMo, GLM ar - Network accessline 339
{reach:65,velocity:50,sentiment:62,riskTopic:35,opp:10,tier:'watch',velDir:'flat',platform:'reddit',head:'r/ClaudeAI: backlash to Anthropic rolling out identity verification',quote:'"I do like Anthropic\u2019s offerings but DS, MiMo, GLM ar - Network accessline 340
{reach:55,velocity:40,sentiment:65,riskTopic:30,opp:8,tier:'watch',velDir:'flat',platform:'reddit',head:'r/Anthropic: "Claude to Require Face ID" — account wrongly flagged as a child\u2019s',quote:'"My Account randomly got flagged as used b - Network accessline 340
{reach:55,velocity:40,sentiment:65,riskTopic:30,opp:8,tier:'watch',velDir:'flat',platform:'reddit',head:'r/Anthropic: "Claude to Require Face ID" — account wrongly flagged as a child\u2019s',quote:'"My Account randomly got flagged as used b - Network accessline 341
{reach:78,velocity:55,sentiment:25,riskTopic:20,opp:35,tier:'watch',velDir:'flat',platform:'news',head:'InfoQ: Claude Fable 5 on Bedrock requires sharing inference data with Anthropic',quote:'"Using Claude Fable 5 or Mythos 5 on Amazon Bedr - Network accessline 341
{reach:78,velocity:55,sentiment:25,riskTopic:20,opp:35,tier:'watch',velDir:'flat',platform:'news',head:'InfoQ: Claude Fable 5 on Bedrock requires sharing inference data with Anthropic',quote:'"Using Claude Fable 5 or Mythos 5 on Amazon Bedr - Network accessline 342
{reach:82,velocity:45,sentiment:5,riskTopic:0,opp:80,tier:'engage',velDir:'flat',platform:'news',head:'Forbes: Anthropic invests $150M to launch 1,000 "Claude Corps" fellowships',quote:'"Anthropic has unveiled Claude Corps, a $150 million i - Network accessline 342
{reach:82,velocity:45,sentiment:5,riskTopic:0,opp:80,tier:'engage',velDir:'flat',platform:'news',head:'Forbes: Anthropic invests $150M to launch 1,000 "Claude Corps" fellowships',quote:'"Anthropic has unveiled Claude Corps, a $150 million i - Network accessline 343
{reach:60,velocity:42,sentiment:8,riskTopic:0,opp:72,tier:'engage',velDir:'flat',platform:'news',head:'Anthropic opens Seoul office, signs MOU with Korea\u2019s Ministry of Science and ICT',quote:'"Anthropic has signed an MOU with Korea\u20 - Network accessline 343
{reach:60,velocity:42,sentiment:8,riskTopic:0,opp:72,tier:'engage',velDir:'flat',platform:'news',head:'Anthropic opens Seoul office, signs MOU with Korea\u2019s Ministry of Science and ICT',quote:'"Anthropic has signed an MOU with Korea\u20 - Network accessline 344
{reach:70,velocity:48,sentiment:10,riskTopic:0,opp:68,tier:'engage',velDir:'flat',platform:'hackernews',head:'Show HN: open-source job-search plugin + skills for Claude Code',quote:'"I wanted to share an open source plugin + skills I put to - Network accessline 344
{reach:70,velocity:48,sentiment:10,riskTopic:0,opp:68,tier:'engage',velDir:'flat',platform:'hackernews',head:'Show HN: open-source job-search plugin + skills for Claude Code',quote:'"I wanted to share an open source plugin + skills I put to - Network accessline 345
{reach:48,velocity:35,sentiment:5,riskTopic:0,opp:55,tier:'engage',velDir:'flat',platform:'x',head:'X: practitioner endorses Claude as a parallel workhorse alongside GPT',quote:'"Claude is still a workhorse at summarizing, writing, creating - Network accessline 345
{reach:48,velocity:35,sentiment:5,riskTopic:0,opp:55,tier:'engage',velDir:'flat',platform:'x',head:'X: practitioner endorses Claude as a parallel workhorse alongside GPT',quote:'"Claude is still a workhorse at summarizing, writing, creating - Network accessline 346
{reach:42,velocity:30,sentiment:3,riskTopic:0,opp:50,tier:'engage',velDir:'flat',platform:'x',head:'X: user expresses delight using Claude for community-event tasks',quote:'"Claude really seems to love helping me w vibecamp tasks. I can\u20 - Network accessline 346
{reach:42,velocity:30,sentiment:3,riskTopic:0,opp:50,tier:'engage',velDir:'flat',platform:'x',head:'X: user expresses delight using Claude for community-event tasks',quote:'"Claude really seems to love helping me w vibecamp tasks. I can\u20 - Network accessline 347
{reach:58,velocity:38,sentiment:45,riskTopic:15,opp:30,tier:'log',velDir:'flat',platform:'reddit',head:'r/singularity: "Personality clashes sent Anthropic\u2019s models offline"',quote:'"Anthropic is killing Opus models for the Pro plan."', - Network accessline 347
{reach:58,velocity:38,sentiment:45,riskTopic:15,opp:30,tier:'log',velDir:'flat',platform:'reddit',head:'r/singularity: "Personality clashes sent Anthropic\u2019s models offline"',quote:'"Anthropic is killing Opus models for the Pro plan."', - Network accessline 348
{reach:50,velocity:25,sentiment:12,riskTopic:0,opp:30,tier:'log',velDir:'down',platform:'x',head:'X: open question on whether Claude performs better in OpenCode/Cursor than Claude Code',quote:'"I often see tweets saying \u2018Claude perform - Network accessline 348
{reach:50,velocity:25,sentiment:12,riskTopic:0,opp:30,tier:'log',velDir:'down',platform:'x',head:'X: open question on whether Claude performs better in OpenCode/Cursor than Claude Code',quote:'"I often see tweets saying \u2018Claude perform - Network accessline 568
const geoPoints=[ {name:'United States', lat:39, lng:-98, tier:'high', sources:[ {head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"', plat:'news', meta:'CNN Business · Jun 21', url:'https://www.cnn.com/20 - Network accessline 568
const geoPoints=[ {name:'United States', lat:39, lng:-98, tier:'high', sources:[ {head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"', plat:'news', meta:'CNN Business · Jun 21', url:'https://www.cnn.com/20 - Network accessline 569
{name:'United States', lat:39, lng:-98, tier:'high', sources:[ {head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"', plat:'news', meta:'CNN Business · Jun 21', url:'https://www.cnn.com/2026/06/21/tech/anthro - Network accessline 569
{name:'United States', lat:39, lng:-98, tier:'high', sources:[ {head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"', plat:'news', meta:'CNN Business · Jun 21', url:'https://www.cnn.com/2026/06/21/tech/anthro - Network accessline 570
{head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"', plat:'news', meta:'CNN Business · Jun 21', url:'https://www.cnn.com/2026/06/21/tech/anthropic-ai-regulation', tier:'high'}, - Network accessline 570
{head:'CNN: "AI regulation is a mess, and Anthropic is caught in the crosshairs"', plat:'news', meta:'CNN Business · Jun 21', url:'https://www.cnn.com/2026/06/21/tech/anthropic-ai-regulation', tier:'high'}, - Network accessline 571
{head:'PBS: Anthropic disables new AI model after White House directive', plat:'news', meta:'PBS NewsHour · Jun 17', url:'https://www.pbs.org/newshour/show/anthropic-disables-new-ai-model-after-white-house-security-directive', tier:'high'}, - Network accessline 571
{head:'PBS: Anthropic disables new AI model after White House directive', plat:'news', meta:'PBS NewsHour · Jun 17', url:'https://www.pbs.org/newshour/show/anthropic-disables-new-ai-model-after-white-house-security-directive', tier:'high'}, - Network accessline 572
{head:'WSJ: Anthropic sued over limits on its $200-a-month AI plans', plat:'news', meta:'Wall Street Journal · Jun 15', url:'https://www.wsj.com/tech/ai/anthropic-sued-over-limits-on-its-200-a-month-ai-plans-e2a109e4', tier:'high'}, - Network accessline 572
{head:'WSJ: Anthropic sued over limits on its $200-a-month AI plans', plat:'news', meta:'Wall Street Journal · Jun 15', url:'https://www.wsj.com/tech/ai/anthropic-sued-over-limits-on-its-200-a-month-ai-plans-e2a109e4', tier:'high'}, - Network accessline 573
{head:'Forbes: Anthropic invests $150M to launch 1,000 Claude Corps fellowships', plat:'news', meta:'Forbes · Jun 18', url:'https://www.forbes.com/sites/michaeltnietzel/2026/06/18/anthropic-invests-150-million-to-launch-1000-claude-corps-fe - Network accessline 573
{head:'Forbes: Anthropic invests $150M to launch 1,000 Claude Corps fellowships', plat:'news', meta:'Forbes · Jun 18', url:'https://www.forbes.com/sites/michaeltnietzel/2026/06/18/anthropic-invests-150-million-to-launch-1000-claude-corps-fe - Network accessline 574
{head:'"Anthropic is losing the mandate of heaven" essay', plat:'x', meta:'@haridigresses · Jun 20', url:'https://x.com/haridigresses/article/2065574450183963134?ref=spyglass.org', tier:'med'}, - Network accessline 574
{head:'"Anthropic is losing the mandate of heaven" essay', plat:'x', meta:'@haridigresses · Jun 20', url:'https://x.com/haridigresses/article/2065574450183963134?ref=spyglass.org', tier:'med'}, - Network accessline 575
{head:'r/ClaudeAI: identity-verification backlash', plat:'reddit', meta:'r/ClaudeAI · Jun 18', url:'https://www.reddit.com/r/ClaudeAI/comments/1uboasr/anthropic_is_rolling_out_identity_verification/', tier:'med'}, - Network accessline 575
{head:'r/ClaudeAI: identity-verification backlash', plat:'reddit', meta:'r/ClaudeAI · Jun 18', url:'https://www.reddit.com/r/ClaudeAI/comments/1uboasr/anthropic_is_rolling_out_identity_verification/', tier:'med'}, - Network accessline 576
{head:'Reuters: Trump no longer views Anthropic as national security threat', plat:'news', meta:'Reuters · Jun 19', url:'https://www.reuters.com/world/us/trump-tells-axios-he-no-longer-views-anthropic-national-security-threat-2026-06-19/', - Network accessline 576
{head:'Reuters: Trump no longer views Anthropic as national security threat', plat:'news', meta:'Reuters · Jun 19', url:'https://www.reuters.com/world/us/trump-tells-axios-he-no-longer-views-anthropic-national-security-threat-2026-06-19/', - Network accessline 577
]}, {name:'South Korea', lat:36, lng:128, tier:'med', sources:[ {head:'Anthropic opens Seoul office, signs MOU with Korea\u2019s Ministry of Science and ICT', plat:'news', meta:'Press · Jun 17', url:'https://www.anthropic.com/news/seo - Network accessline 577
]}, {name:'South Korea', lat:36, lng:128, tier:'med', sources:[ {head:'Anthropic opens Seoul office, signs MOU with Korea\u2019s Ministry of Science and ICT', plat:'news', meta:'Press · Jun 17', url:'https://www.anthropic.com/news/seo - Network accessline 578
{name:'South Korea', lat:36, lng:128, tier:'med', sources:[ {head:'Anthropic opens Seoul office, signs MOU with Korea\u2019s Ministry of Science and ICT', plat:'news', meta:'Press · Jun 17', url:'https://www.anthropic.com/news/seoul-off - Network accessline 578
{name:'South Korea', lat:36, lng:128, tier:'med', sources:[ {head:'Anthropic opens Seoul office, signs MOU with Korea\u2019s Ministry of Science and ICT', plat:'news', meta:'Press · Jun 17', url:'https://www.anthropic.com/news/seoul-off - Network accessline 579
{head:'Anthropic opens Seoul office, signs MOU with Korea\u2019s Ministry of Science and ICT', plat:'news', meta:'Press · Jun 17', url:'https://www.anthropic.com/news/seoul-office-partnerships-korean-ai-ecosystem', tier:'low'}, - Network accessline 579
{head:'Anthropic opens Seoul office, signs MOU with Korea\u2019s Ministry of Science and ICT', plat:'news', meta:'Press · Jun 17', url:'https://www.anthropic.com/news/seoul-office-partnerships-korean-ai-ecosystem', tier:'low'}, - Network accessline 580
]}, {name:'United Kingdom', lat:54, lng:-2, tier:'low', sources:[ {head:'BBC: Anthropic to meet White House over AI tool suspension', plat:'news', meta:'BBC News · Jun 16', url:'https://www.bbc.com/news/articles/c9w2p7ykp8yo', tier:'m - Network accessline 580
]}, {name:'United Kingdom', lat:54, lng:-2, tier:'low', sources:[ {head:'BBC: Anthropic to meet White House over AI tool suspension', plat:'news', meta:'BBC News · Jun 16', url:'https://www.bbc.com/news/articles/c9w2p7ykp8yo', tier:'m - Network accessline 581
{name:'United Kingdom', lat:54, lng:-2, tier:'low', sources:[ {head:'BBC: Anthropic to meet White House over AI tool suspension', plat:'news', meta:'BBC News · Jun 16', url:'https://www.bbc.com/news/articles/c9w2p7ykp8yo', tier:'med'}, - Network accessline 581
{name:'United Kingdom', lat:54, lng:-2, tier:'low', sources:[ {head:'BBC: Anthropic to meet White House over AI tool suspension', plat:'news', meta:'BBC News · Jun 16', url:'https://www.bbc.com/news/articles/c9w2p7ykp8yo', tier:'med'}, - Network accessline 582
{head:'BBC: Anthropic to meet White House over AI tool suspension', plat:'news', meta:'BBC News · Jun 16', url:'https://www.bbc.com/news/articles/c9w2p7ykp8yo', tier:'med'}, - Network accessline 582
{head:'BBC: Anthropic to meet White House over AI tool suspension', plat:'news', meta:'BBC News · Jun 16', url:'https://www.bbc.com/news/articles/c9w2p7ykp8yo', tier:'med'}, - Network accessline 621
} const srcs=[ 'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', - Network accessline 621
} const srcs=[ 'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', - Network accessline 622
const srcs=[ 'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', 'https://unpkg.com/world-atlas@2.0.2/countries-110m.json', - Network accessline 622
const srcs=[ 'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', 'https://unpkg.com/world-atlas@2.0.2/countries-110m.json', - Network accessline 623
'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', - Network accessline 623
'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', - Network accessline 624
'https://unpkg.com/world-atlas@2.0.2/countries-110m.json', - Network accessline 624
'https://unpkg.com/world-atlas@2.0.2/countries-110m.json', - Network accessline 625
'https://cdnjs.cloudflare.com/ajax/libs/world-atlas/2.0.2/countries-110m.json' - Network accessline 625
'https://cdnjs.cloudflare.com/ajax/libs/world-atlas/2.0.2/countries-110m.json' - Network accessline 627
function tryLoad(i){ if(i>=srcs.length){svg.append('text').attr('x',W/2).attr('y',H/2).attr('text-anchor','middle').attr('fill','var(--color-text-secondary)').attr('font-size',13).text('Map unavailable');return;} fetch(srcs[i]).then - Network accessline 627
function tryLoad(i){ if(i>=srcs.length){svg.append('text').attr('x',W/2).attr('y',H/2).attr('text-anchor','middle').attr('fill','var(--color-text-secondary)').attr('font-size',13).text('Map unavailable');return;} fetch(srcs[i]).then - Network accessline 628
if(i>=srcs.length){svg.append('text').attr('x',W/2).attr('y',H/2).attr('text-anchor','middle').attr('fill','var(--color-text-secondary)').attr('font-size',13).text('Map unavailable');return;} fetch(srcs[i]).then(r=>{if(!r.ok)throw 0;ret - Network accessline 628
if(i>=srcs.length){svg.append('text').attr('x',W/2).attr('y',H/2).attr('text-anchor','middle').attr('fill','var(--color-text-secondary)').attr('font-size',13).text('Map unavailable');return;} fetch(srcs[i]).then(r=>{if(!r.ok)throw 0;ret - Network accessline 629
fetch(srcs[i]).then(r=>{if(!r.ok)throw 0;return r.json();}).then(world=>{ - Network accessline 629
fetch(srcs[i]).then(r=>{if(!r.ok)throw 0;return r.json();}).then(world=>{
skills/brand-mention-monitor/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/brand-mention-monitor/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/brand-mention-monitor/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/brand-mention-monitor/references/template.html
- Network accessline 23
SOURCE URL RULE — CRITICAL: Every mention url must be the EXACT Nimble result URL — never a homepage. CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' - Network accessline 23
SOURCE URL RULE — CRITICAL: Every mention url must be the EXACT Nimble result URL — never a homepage. CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' - Network accessline 24
Every mention url must be the EXACT Nimble result URL — never a homepage. CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' CORRECT: 'https://x.com/username/status/1234567890' - Network accessline 24
Every mention url must be the EXACT Nimble result URL — never a homepage. CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' CORRECT: 'https://x.com/username/status/1234567890' - Network accessline 25
CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' - Network accessline 25
CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' - Network accessline 26
CORRECT: 'https://x.com/username/status/1234567890' - Network accessline 26
CORRECT: 'https://x.com/username/status/1234567890' - Network accessline 27
WRONG: 'https://reddit.com' WRONG: 'https://x.com' - Network accessline 27
WRONG: 'https://reddit.com' WRONG: 'https://x.com' - Network accessline 419
<script src="https://cdnjs.cloudflare.com/ajax/libs/d3/7.8.5/d3.min.js"></script> - Network accessline 419
<script src="https://cdnjs.cloudflare.com/ajax/libs/d3/7.8.5/d3.min.js"></script> - Network accessline 420
<script src="https://cdnjs.cloudflare.com/ajax/libs/topojson/3.0.2/topojson.min.js"></script> - Network accessline 420
<script src="https://cdnjs.cloudflare.com/ajax/libs/topojson/3.0.2/topojson.min.js"></script> - Network accessline 434
// // URL RULE — every url must be the EXACT Nimble result URL, never a homepage: // CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' - Network accessline 434
// // URL RULE — every url must be the EXACT Nimble result URL, never a homepage: // CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' - Network accessline 435
// URL RULE — every url must be the EXACT Nimble result URL, never a homepage: // CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' // CORRECT: 'https://x.com/username/status/1234567890' - Network accessline 435
// URL RULE — every url must be the EXACT Nimble result URL, never a homepage: // CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' // CORRECT: 'https://x.com/username/status/1234567890' - Network accessline 436
// CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' - Network accessline 436
// CORRECT: 'https://reddit.com/r/SaaS/comments/abc123/title' - Network accessline 437
// CORRECT: 'https://x.com/username/status/1234567890' - Network accessline 437
// CORRECT: 'https://x.com/username/status/1234567890' - Network accessline 438
// WRONG: 'https://reddit.com' WRONG: 'https://x.com' - Network accessline 438
// WRONG: 'https://reddit.com' WRONG: 'https://x.com' - Network accessline 881
} const sources=[ 'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', - Network accessline 881
} const sources=[ 'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', - Network accessline 882
const sources=[ 'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', 'https://unpkg.com/world-atlas@2.0.2/countries-110m.json', - Network accessline 882
const sources=[ 'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', 'https://unpkg.com/world-atlas@2.0.2/countries-110m.json', - Network accessline 883
'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', - Network accessline 883
'https://cdn.jsdelivr.net/npm/world-atlas@2.0.2/countries-110m.json', - Network accessline 884
'https://unpkg.com/world-atlas@2.0.2/countries-110m.json', - Network accessline 884
'https://unpkg.com/world-atlas@2.0.2/countries-110m.json', - Network accessline 885
'https://cdnjs.cloudflare.com/ajax/libs/world-atlas/2.0.2/countries-110m.json' - Network accessline 885
'https://cdnjs.cloudflare.com/ajax/libs/world-atlas/2.0.2/countries-110m.json' - Network accessline 890
return; } fetch(sources[i]).then(r=>{if(!r.ok)throw 0;return r.json();}).then(world=>{ - Network accessline 890
return; } fetch(sources[i]).then(r=>{if(!r.ok)throw 0;return r.json();}).then(world=>{ - Network accessline 891
} fetch(sources[i]).then(r=>{if(!r.ok)throw 0;return r.json();}).then(world=>{ const feat=topojson.feature(world,world.objects.countries); - Network accessline 891
} fetch(sources[i]).then(r=>{if(!r.ok)throw 0;return r.json();}).then(world=>{ const feat=topojson.feature(world,world.objects.countries); - Network accessline 892
fetch(sources[i]).then(r=>{if(!r.ok)throw 0;return r.json();}).then(world=>{ - Network accessline 892
fetch(sources[i]).then(r=>{if(!r.ok)throw 0;return r.json();}).then(world=>{
skills/company-deep-dive/SKILL.md
skills/company-deep-dive/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/company-deep-dive/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/company-deep-dive/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/competitor-intel/SKILL.md
skills/competitor-intel/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/competitor-intel/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/competitor-intel/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/competitor-positioning/SKILL.md
- Broad permissionsline 1
Bash(python3:*) - Broad permissionsline 1
Bash(python3:*) - Network accessline 137
`nimble --transform "links.#.url" map --url "https://[company-domain]" --sitemap only --limit 200` - Network accessline 137
`nimble --transform "links.#.url" map --url "https://[company-domain]" --sitemap only --limit 200` - Network accessline 144
- `nimble extract --url "https://[company-domain]" --format markdown` - Network accessline 144
- `nimble extract --url "https://[company-domain]" --format markdown`
skills/competitor-positioning/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/competitor-positioning/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/competitor-positioning/references/positioning-agent-prompt.md
- Network accessline 28
1. nimble --transform "links.#.url" map --url "https://[competitor-domain]" --sitemap only --limit 200 - Network accessline 28
1. nimble --transform "links.#.url" map --url "https://[competitor-domain]" --sitemap only --limit 200 - Network accessline 30
From the returned URL list, identify the best pages for positioning analysis: - Homepage: https://[competitor-domain] (always extract this) - Network accessline 30
From the returned URL list, identify the best pages for positioning analysis: - Homepage: https://[competitor-domain] (always extract this) - Network accessline 31
- Homepage: https://[competitor-domain] (always extract this) - Network accessline 31
- Homepage: https://[competitor-domain] (always extract this) - Network accessline 47
2. nimble extract --url "https://[competitor-domain]" --format markdown - Network accessline 47
2. nimble extract --url "https://[competitor-domain]" --format markdown
skills/competitor-positioning/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/credit-risk/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Broad permissionsline 1
Bash(npm --version) - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 129
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 129
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 130
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 130
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 136
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc - Network accessline 136
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/deal-sourcing/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Broad permissionsline 1
Bash(npm --version) - Network accessline 74
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 74
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 131
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 132
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 132
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 138
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc - Network accessline 138
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/decision-maker-identification/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Broad permissionsline 1
Bash(npm --version) - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 130
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 130
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 137
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc - Network accessline 137
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/due-diligence/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Broad permissionsline 1
Bash(npm --version) - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 129
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 129
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 130
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 130
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 136
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc - Network accessline 136
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/healthcare-providers-enrich/SKILL.md
skills/healthcare-providers-enrich/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/healthcare-providers-enrich/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/healthcare-providers-enrich/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/healthcare-providers-extract/SKILL.md
- Broad permissionsline 1
Bash(python3:*) - Broad permissionsline 1
Bash(python3:*) - Network accessline 214
"contact": {"phone": "(555) 123-4567", "scheduling_url": "..."}, "education": "Fellowship: Bascom Palmer Eye Institute", "source_url": "https://practice.com/our-doctors", - Network accessline 214
"contact": {"phone": "(555) 123-4567", "scheduling_url": "..."}, "education": "Fellowship: Bascom Palmer Eye Institute", "source_url": "https://practice.com/our-doctors", - Network accessline 215
"education": "Fellowship: Bascom Palmer Eye Institute", "source_url": "https://practice.com/our-doctors", "practice_name": "Shore Center for Eye Care", - Network accessline 215
"education": "Fellowship: Bascom Palmer Eye Institute", "source_url": "https://practice.com/our-doctors", "practice_name": "Shore Center for Eye Care", - Network accessline 216
"source_url": "https://practice.com/our-doctors", - Network accessline 216
"source_url": "https://practice.com/our-doctors", - Network accessline 217
"practice_name": "Shore Center for Eye Care", "practice_url": "https://practice.com", "confidence": "High" - Network accessline 217
"practice_name": "Shore Center for Eye Care", "practice_url": "https://practice.com", "confidence": "High" - Network accessline 218
"practice_url": "https://practice.com", - Network accessline 218
"practice_url": "https://practice.com",
skills/healthcare-providers-extract/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/healthcare-providers-extract/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/healthcare-providers-extract/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/healthcare-providers-verify/SKILL.md
- Broad permissionsline 1
Bash(python3:*) - Broad permissionsline 1
Bash(python3:*) - Network accessline 157
nimble extract --url "https://npiregistry.cms.hhs.gov/api/?version=2.1&first_name=[First]&last_name=[Last]&state=[ST]&limit=5" --format markdown - Network accessline 157
nimble extract --url "https://npiregistry.cms.hhs.gov/api/?version=2.1&first_name=[First]&last_name=[Last]&state=[ST]&limit=5" --format markdown
skills/healthcare-providers-verify/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/healthcare-providers-verify/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/healthcare-providers-verify/references/npi-verification-patterns.md
- Network accessline 22
nimble extract --url "https://npiregistry.cms.hhs.gov/api/?version=2.1&first_name=[First]&last_name=[Last]&state=[ST]&limit=5" --format markdown - Network accessline 22
nimble extract --url "https://npiregistry.cms.hhs.gov/api/?version=2.1&first_name=[First]&last_name=[Last]&state=[ST]&limit=5" --format markdown
skills/healthcare-providers-verify/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/kyc-screening/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Broad permissionsline 1
Bash(npm --version) - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 130
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 130
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 137
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc - Network accessline 137
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/launch-monitor/SKILL.md
- Broad permissionsline 1
Bash(python3:*) - Broad permissionsline 1
Bash(python3:*) - Network accessline 238
**CORRECT — exact article/thread/post URLs:** - `https://techcrunch.com/2026/06/11/nimble-mcp-connector-launch` - Network accessline 238
**CORRECT — exact article/thread/post URLs:** - `https://techcrunch.com/2026/06/11/nimble-mcp-connector-launch` - Network accessline 239
- `https://techcrunch.com/2026/06/11/nimble-mcp-connector-launch` - Network accessline 239
- `https://techcrunch.com/2026/06/11/nimble-mcp-connector-launch` - Network accessline 240
- `https://news.ycombinator.com/item?id=12345678` - Network accessline 240
- `https://news.ycombinator.com/item?id=12345678` - Network accessline 241
- `https://reddit.com/r/MachineLearning/comments/abc123/is_nimble_just_another_scraper` - Network accessline 241
- `https://reddit.com/r/MachineLearning/comments/abc123/is_nimble_just_another_scraper` - Network accessline 242
- `https://x.com/[username]/status/[POST_ID]` - Network accessline 242
- `https://x.com/[username]/status/[POST_ID]` - Network accessline 244
**WRONG — never use these:** - `https://techcrunch.com` - Network accessline 244
**WRONG — never use these:** - `https://techcrunch.com` - Network accessline 245
- `https://techcrunch.com` - Network accessline 245
- `https://techcrunch.com` - Network accessline 246
- `https://news.ycombinator.com` - Network accessline 246
- `https://news.ycombinator.com` - Network accessline 247
- `https://reddit.com` - Network accessline 247
- `https://reddit.com` - Network accessline 248
- `https://x.com` - Network accessline 248
- `https://x.com`
skills/launch-monitor/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/launch-monitor/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/launch-monitor/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/launch-monitor/references/template.html
- Network accessline 218
// URL RULE — DO NOT USE HOMEPAGES. Every url field must be the exact URL // returned by Nimble for that specific article, post, or thread. // CORRECT: 'https://techcrunch.com/2026/06/11/nimble-mcp-launch' - Network accessline 218
// URL RULE — DO NOT USE HOMEPAGES. Every url field must be the exact URL // returned by Nimble for that specific article, post, or thread. // CORRECT: 'https://techcrunch.com/2026/06/11/nimble-mcp-launch' - Network accessline 219
// returned by Nimble for that specific article, post, or thread. // CORRECT: 'https://techcrunch.com/2026/06/11/nimble-mcp-launch' // CORRECT: 'https://news.ycombinator.com/item?id=12345678' - Network accessline 219
// returned by Nimble for that specific article, post, or thread. // CORRECT: 'https://techcrunch.com/2026/06/11/nimble-mcp-launch' // CORRECT: 'https://news.ycombinator.com/item?id=12345678' - Network accessline 220
// CORRECT: 'https://techcrunch.com/2026/06/11/nimble-mcp-launch' - Network accessline 220
// CORRECT: 'https://techcrunch.com/2026/06/11/nimble-mcp-launch' - Network accessline 221
// CORRECT: 'https://news.ycombinator.com/item?id=12345678' - Network accessline 221
// CORRECT: 'https://news.ycombinator.com/item?id=12345678' - Network accessline 222
// CORRECT: 'https://reddit.com/r/MachineLearning/comments/abc123/title_here' - Network accessline 222
// CORRECT: 'https://reddit.com/r/MachineLearning/comments/abc123/title_here' - Network accessline 223
// WRONG: 'https://techcrunch.com' - Network accessline 223
// WRONG: 'https://techcrunch.com' - Network accessline 224
// WRONG: 'https://news.ycombinator.com' - Network accessline 224
// WRONG: 'https://news.ycombinator.com' - Network accessline 225
// WRONG: 'https://reddit.com' - Network accessline 225
// WRONG: 'https://reddit.com'
skills/local-places/SKILL.md
- Broad permissionsline 1
Bash(python3:*) - Broad permissionsline 1
Bash(python3:*) - Network accessline 299
### 1. Place A - **Address:** 123 Main St, Williamsburg, Brooklyn, NY - **Phone:** (555) 123-4567 | **Website:** [placea.com](https://placea.com) - Network accessline 299
### 1. Place A - **Address:** 123 Main St, Williamsburg, Brooklyn, NY - **Phone:** (555) 123-4567 | **Website:** [placea.com](https://placea.com) - Network accessline 300
- **Address:** 123 Main St, Williamsburg, Brooklyn, NY - **Phone:** (555) 123-4567 | **Website:** [placea.com](https://placea.com) - **Rating:** 4.8/5 (312 reviews on Google Maps, 289 on Yelp) - Network accessline 300
- **Address:** 123 Main St, Williamsburg, Brooklyn, NY - **Phone:** (555) 123-4567 | **Website:** [placea.com](https://placea.com) - **Rating:** 4.8/5 (312 reviews on Google Maps, 289 on Yelp) - Network accessline 301
- **Phone:** (555) 123-4567 | **Website:** [placea.com](https://placea.com) - Network accessline 301
- **Phone:** (555) 123-4567 | **Website:** [placea.com](https://placea.com)
skills/local-places/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/local-places/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/local-places/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/market-finder/SKILL.md
skills/market-finder/references/audit-mode.md
skills/market-finder/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/market-finder/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/market-finder/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/meeting-prep/SKILL.md
skills/meeting-prep/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/meeting-prep/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/meeting-prep/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/nimble-databricks-data-products/SKILL.md
skills/nimble-databricks-data-products/references/branding.md
- Network accessline 18
function PoweredByNimble({ className = '' }: { className?: string }) { return ( <a href="https://www.nimbleway.com" target="_blank" rel="noopener noreferrer" - Network accessline 18
function PoweredByNimble({ className = '' }: { className?: string }) { return ( <a href="https://www.nimbleway.com" target="_blank" rel="noopener noreferrer" - Network accessline 19
return ( <a href="https://www.nimbleway.com" target="_blank" rel="noopener noreferrer" className={`inline-flex items-center gap-2 group ${className}`} aria-label="Powered by Nimble"> - Network accessline 19
return ( <a href="https://www.nimbleway.com" target="_blank" rel="noopener noreferrer" className={`inline-flex items-center gap-2 group ${className}`} aria-label="Powered by Nimble"> - Network accessline 20
<a href="https://www.nimbleway.com" target="_blank" rel="noopener noreferrer" - Network accessline 20
<a href="https://www.nimbleway.com" target="_blank" rel="noopener noreferrer"
skills/nimble-databricks-data-products/references/databricks-skills.md
- Network accessline 3
This skill is **not** a Databricks tutorial. For generic Databricks mechanics, use the official skills and follow their guidance. Repo: <https://github.com/databricks/databricks-agent-skills/tree/main/skills> - Network accessline 3
This skill is **not** a Databricks tutorial. For generic Databricks mechanics, use the official skills and follow their guidance. Repo: <https://github.com/databricks/databricks-agent-skills/tree/main/skills> - Network accessline 4
skills and follow their guidance. Repo: <https://github.com/databricks/databricks-agent-skills/tree/main/skills> - Network accessline 4
skills and follow their guidance. Repo: <https://github.com/databricks/databricks-agent-skills/tree/main/skills>
skills/nimble-databricks-data-products/references/install-nimble-integration.md
- Network accessline 8
Authoritative source: **Nimble cookbook for Databricks** — <https://github.com/Nimbleway/cookbook/tree/main/databricks> - Network accessline 8
Authoritative source: **Nimble cookbook for Databricks** — <https://github.com/Nimbleway/cookbook/tree/main/databricks> - Network accessline 9
<https://github.com/Nimbleway/cookbook/tree/main/databricks> - Network accessline 9
<https://github.com/Nimbleway/cookbook/tree/main/databricks> - Network accessline 20
This lets the warehouse make the outbound call to Nimble's API endpoint. - Permission to create catalogs/schemas and `CREATE FUNCTION`. - A Nimble API key: <https://online.nimbleway.com/account-settings/api-keys> - Network accessline 20
This lets the warehouse make the outbound call to Nimble's API endpoint. - Permission to create catalogs/schemas and `CREATE FUNCTION`. - A Nimble API key: <https://online.nimbleway.com/account-settings/api-keys> - Network accessline 21
- Permission to create catalogs/schemas and `CREATE FUNCTION`. - A Nimble API key: <https://online.nimbleway.com/account-settings/api-keys> - Databricks CLI v0.205+ authenticated (`databricks auth login`). - Network accessline 21
- Permission to create catalogs/schemas and `CREATE FUNCTION`. - A Nimble API key: <https://online.nimbleway.com/account-settings/api-keys> - Databricks CLI v0.205+ authenticated (`databricks auth login`). - Network accessline 22
- A Nimble API key: <https://online.nimbleway.com/account-settings/api-keys> - Network accessline 22
- A Nimble API key: <https://online.nimbleway.com/account-settings/api-keys> - Access to secretsline 30
[Credential-related source omitted] - Access to secretsline 30
[Credential-related source omitted] - Network accessline 49
SELECT count(*) AS n FROM nimble_integration.tools.nimble_search('AI agents news', 5); SELECT length(content) FROM nimble_integration.tools.nimble_extract('https://www.nimbleway.com'); - Network accessline 49
SELECT count(*) AS n FROM nimble_integration.tools.nimble_search('AI agents news', 5); SELECT length(content) FROM nimble_integration.tools.nimble_extract('https://www.nimbleway.com'); - Network accessline 50
SELECT length(content) FROM nimble_integration.tools.nimble_extract('https://www.nimbleway.com'); - Network accessline 50
SELECT length(content) FROM nimble_integration.tools.nimble_extract('https://www.nimbleway.com');
skills/nimble-databricks-data-products/scripts/build_dashboard.py
- Executable scriptline 1
#!/usr/bin/env python3 - Executable scriptline 1
#!/usr/bin/env python3 - Network accessline 299
print(json.dumps({ "dashboard_id": did, "editor": f"https://{host}/dashboardsv3/{did}/editor", - Network accessline 299
print(json.dumps({ "dashboard_id": did, "editor": f"https://{host}/dashboardsv3/{did}/editor", - Network accessline 300
"dashboard_id": did, "editor": f"https://{host}/dashboardsv3/{did}/editor", "published": f"https://{host}/dashboardsv3/{did}/published", - Network accessline 300
"dashboard_id": did, "editor": f"https://{host}/dashboardsv3/{did}/editor", "published": f"https://{host}/dashboardsv3/{did}/published", - Network accessline 301
"editor": f"https://{host}/dashboardsv3/{did}/editor", - Network accessline 301
"editor": f"https://{host}/dashboardsv3/{did}/editor", - Network accessline 302
"published": f"https://{host}/dashboardsv3/{did}/published", - Network accessline 302
"published": f"https://{host}/dashboardsv3/{did}/published",
skills/nimble-databricks-data-products/scripts/ingest.sh
skills/nimble-web-expert/README.md
- Network accessline 3
[](https://opensource.org/licenses/MIT) - Network accessline 3
[](https://opensource.org/licenses/MIT) - Network accessline 21
- **Nimble CLI** — installed and authenticated (`nimble --version` to verify) - **Nimble API key** — [online.nimbleway.com/signup](https://online.nimbleway.com/signup) - Network accessline 21
- **Nimble CLI** — installed and authenticated (`nimble --version` to verify) - **Nimble API key** — [online.nimbleway.com/signup](https://online.nimbleway.com/signup) - Network accessline 22
- **Nimble API key** — [online.nimbleway.com/signup](https://online.nimbleway.com/signup) - Network accessline 22
- **Nimble API key** — [online.nimbleway.com/signup](https://online.nimbleway.com/signup) - Network accessline 33
claude mcp add --transport http nimble-docs https://docs.nimbleway.com/mcp - Network accessline 33
claude mcp add --transport http nimble-docs https://docs.nimbleway.com/mcp - Network accessline 48
Each command supports multiple output formats — see [docs.nimbleway.com](https://docs.nimbleway.com) for the full flag reference. - Network accessline 48
Each command supports multiple output formats — see [docs.nimbleway.com](https://docs.nimbleway.com) for the full flag reference.
skills/nimble-web-expert/SKILL.md
- Broad permissionsline 1
Bash(python3:*) - Broad permissionsline 1
Bash(python3:*) - Network accessline 64
version: 1.9.0 author: Nimbleway repository: https://github.com/Nimbleway/agent-skills - Network accessline 64
version: 1.9.0 author: Nimbleway repository: https://github.com/Nimbleway/agent-skills - Network accessline 65
author: Nimbleway repository: https://github.com/Nimbleway/agent-skills category: web-search-tools - Network accessline 65
author: Nimbleway repository: https://github.com/Nimbleway/agent-skills category: web-search-tools - Network accessline 66
repository: https://github.com/Nimbleway/agent-skills - Network accessline 66
repository: https://github.com/Nimbleway/agent-skills - Access to secretsline 86
[Credential-related source omitted] - Access to secretsline 86
[Credential-related source omitted] - Access to secretsline 119
[Credential-related source omitted] - Access to secretsline 119
[Credential-related source omitted] - Network accessline 270
- **NEVER retry the same render tier.** If a tier returns empty or truncated content, escalate — do not re-run. - **NEVER escalate at an access barrier.** A CAPTCHA, a human-verification page, or a sign-in wall in place of the target is a r - Network accessline 270
- **NEVER retry the same render tier.** If a tier returns empty or truncated content, escalate — do not re-run. - **NEVER escalate at an access barrier.** A CAPTCHA, a human-verification page, or a sign-in wall in place of the target is a r - Network accessline 271
- **NEVER escalate at an access barrier.** A CAPTCHA, a human-verification page, or a sign-in wall in place of the target is a real outcome — report it plainly and stop. Where a supported alternative exists, take it: `--focus social` search - Network accessline 271
- **NEVER escalate at an access barrier.** A CAPTCHA, a human-verification page, or a sign-in wall in place of the target is a real outcome — report it plainly and stop. Where a supported alternative exists, take it: `--focus social` search - Network accessline 272
- **NEVER substitute WebFetch, WebSearch, curl, or wget for nimble operations.** They're not in `allowed-tools` — if a Nimble transport isn't available, stop and follow the guidance in the no-transport branch of Core principles. Don't try t - Network accessline 272
- **NEVER substitute WebFetch, WebSearch, curl, or wget for nimble operations.** They're not in `allowed-tools` — if a Nimble transport isn't available, stop and follow the guidance in the no-transport branch of Core principles. Don't try t
skills/nimble-web-expert/references/batch-patterns.md
- Network accessline 84
nimble --transform "data.markdown" extract --url "https://example.com/page1" --format markdown > .nimble/page1.md & - Network accessline 84
nimble --transform "data.markdown" extract --url "https://example.com/page1" --format markdown > .nimble/page1.md & - Network accessline 85
nimble --transform "data.markdown" extract --url "https://example.com/page2" --format markdown > .nimble/page2.md & - Network accessline 85
nimble --transform "data.markdown" extract --url "https://example.com/page2" --format markdown > .nimble/page2.md & - Network accessline 86
nimble --transform "data.markdown" extract --url "https://example.com/page3" --format markdown > .nimble/page3.md & - Network accessline 86
nimble --transform "data.markdown" extract --url "https://example.com/page3" --format markdown > .nimble/page3.md & - Network accessline 93
mkdir -p .nimble urls=( "https://example.com/page1" - Network accessline 93
mkdir -p .nimble urls=( "https://example.com/page1" - Network accessline 94
urls=( "https://example.com/page1" "https://example.com/page2" - Network accessline 94
urls=( "https://example.com/page1" "https://example.com/page2" - Network accessline 95
"https://example.com/page1" - Network accessline 95
"https://example.com/page1" - Network accessline 96
"https://example.com/page2" - Network accessline 96
"https://example.com/page2" - Network accessline 97
"https://example.com/page3" - Network accessline 97
"https://example.com/page3" - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Network accessline 243
URLS = [ "https://example.com/page1", - Network accessline 243
URLS = [ "https://example.com/page1", - Network accessline 244
"https://example.com/page1", - Network accessline 244
"https://example.com/page1", - Network accessline 245
"https://example.com/page2", - Network accessline 245
"https://example.com/page2", - Access to secretsline 266
[Credential-related source omitted] - Access to secretsline 266
[Credential-related source omitted]
skills/nimble-web-expert/references/error-handling.md
- Access to secretsline 15
[Credential-related source omitted] - Access to secretsline 15
[Credential-related source omitted] - Network accessline 87
# Attempt 1 — default 30s nimble extract --url "https://example.com" --render --format markdown - Network accessline 87
# Attempt 1 — default 30s nimble extract --url "https://example.com" --render --format markdown - Network accessline 88
nimble extract --url "https://example.com" --render --format markdown - Network accessline 88
nimble extract --url "https://example.com" --render --format markdown - Network accessline 90
# Attempt 2 — 60s nimble extract --url "https://example.com" --render \ - Network accessline 90
# Attempt 2 — 60s nimble extract --url "https://example.com" --render \ - Network accessline 91
nimble extract --url "https://example.com" --render \ - Network accessline 91
nimble extract --url "https://example.com" --render \ - Network accessline 94
# Attempt 3 — 90s, wait for full network idle nimble extract --url "https://example.com" --render \ - Network accessline 94
# Attempt 3 — 90s, wait for full network idle nimble extract --url "https://example.com" --render \ - Network accessline 95
nimble extract --url "https://example.com" --render \ - Network accessline 95
nimble extract --url "https://example.com" --render \
skills/nimble-web-expert/references/nimble-agents/reference.md
skills/nimble-web-expert/references/nimble-crawl/reference.md
- Network accessline 50
nimble crawl run --url "https://docs.example.com" --limit 50 --name "docs-crawl" - Network accessline 50
nimble crawl run --url "https://docs.example.com" --limit 50 --name "docs-crawl" - Access to secretsline 57
[Credential-related source omitted] - Access to secretsline 57
[Credential-related source omitted] - Network accessline 59
resp = nimble.crawl.run(url="https://docs.example.com", limit=50, name="docs-crawl") - Network accessline 59
resp = nimble.crawl.run(url="https://docs.example.com", limit=50, name="docs-crawl") - Network accessline 153
CRAWL_ID=$(nimble crawl run --url "https://example.com" --limit 100 --name "my-crawl" \ - Network accessline 153
CRAWL_ID=$(nimble crawl run --url "https://example.com" --limit 100 --name "my-crawl" \
skills/nimble-web-expert/references/nimble-extract/browser-actions.md
- Network accessline 13
Docs: https://docs.nimbleway.com/nimble-sdk/web-tools/extract/features/browser-actions - Network accessline 13
Docs: https://docs.nimbleway.com/nimble-sdk/web-tools/extract/features/browser-actions - Network accessline 52
nimble = Nimble() resp = nimble.extract( url="https://example.com/product", - Network accessline 52
nimble = Nimble() resp = nimble.extract( url="https://example.com/product", - Network accessline 53
resp = nimble.extract( url="https://example.com/product", render=True, - Network accessline 53
resp = nimble.extract( url="https://example.com/product", render=True, - Network accessline 54
url="https://example.com/product", - Network accessline 54
url="https://example.com/product", - Access to secretsline 82
[Credential-related source omitted] - Access to secretsline 82
[Credential-related source omitted] - Access to secretsline 83
[Credential-related source omitted] - Access to secretsline 83
[Credential-related source omitted] - Network accessline 98
// Direct form — GET request {"fetch": "https://api.example.com/data"} - Network accessline 98
// Direct form — GET request {"fetch": "https://api.example.com/data"} - Network accessline 99
{"fetch": "https://api.example.com/data"} - Network accessline 99
{"fetch": "https://api.example.com/data"} - Network accessline 102
{ "fetch": { "url": "https://api.example.com/submit", - Network accessline 102
{ "fetch": { "url": "https://api.example.com/submit", - Network accessline 103
"fetch": { "url": "https://api.example.com/submit", "method": "POST", - Network accessline 103
"fetch": { "url": "https://api.example.com/submit", "method": "POST", - Network accessline 104
"url": "https://api.example.com/submit", - Network accessline 104
"url": "https://api.example.com/submit", - Network accessline 128
# Direct form — GET from browser context nimble extract --url "https://example.com" --render \ - Network accessline 128
# Direct form — GET from browser context nimble extract --url "https://example.com" --render \ - Network accessline 129
nimble extract --url "https://example.com" --render \ - Network accessline 129
nimble extract --url "https://example.com" --render \ - Network accessline 131
{"fetch": "https://api.example.com/data"} - Network accessline 131
{"fetch": "https://api.example.com/data"} - Network accessline 134
# Extended form — POST with JSON body (replicate a form submission) nimble extract --url "https://example.com/careers/apply" --render \ - Network accessline 134
# Extended form — POST with JSON body (replicate a form submission) nimble extract --url "https://example.com/careers/apply" --render \ - Network accessline 135
nimble extract --url "https://example.com/careers/apply" --render \ - Network accessline 135
nimble extract --url "https://example.com/careers/apply" --render \ - Network accessline 138
"url": "https://api.example.com/v1/apply", - Network accessline 138
"url": "https://api.example.com/v1/apply", - Network accessline 149
# Direct form — GET resp = nimble.extract( url="https://example.com", - Network accessline 149
# Direct form — GET resp = nimble.extract( url="https://example.com", - Network accessline 150
resp = nimble.extract( url="https://example.com", render=True, - Network accessline 150
resp = nimble.extract( url="https://example.com", render=True, - Network accessline 151
url="https://example.com", - Network accessline 151
url="https://example.com", - Network accessline 152
render=True, browser_actions=[ {"fetch": "https://api.example.com/data"}, - Network accessline 152
render=True, browser_actions=[ {"fetch": "https://api.example.com/data"}, - Network accessline 153
browser_actions=[ {"fetch": "https://api.example.com/data"}, ], - Network accessline 153
browser_actions=[ {"fetch": "https://api.example.com/data"}, ], - Network accessline 154
{"fetch": "https://api.example.com/data"}, - Network accessline 154
{"fetch": "https://api.example.com/data"}, - Network accessline 159
import json resp = nimble.extract( url="https://example.com/careers/apply", - Network accessline 159
import json resp = nimble.extract( url="https://example.com/careers/apply", - Network accessline 160
resp = nimble.extract( url="https://example.com/careers/apply", render=True, - Network accessline 160
resp = nimble.extract( url="https://example.com/careers/apply", render=True, - Network accessline 161
url="https://example.com/careers/apply", - Network accessline 161
url="https://example.com/careers/apply", - Network accessline 164
{ "fetch": { "url": "https://api.example.com/v1/apply", - Network accessline 164
{ "fetch": { "url": "https://api.example.com/v1/apply", - Network accessline 165
"fetch": { "url": "https://api.example.com/v1/apply", "method": "POST", - Network accessline 165
"fetch": { "url": "https://api.example.com/v1/apply", "method": "POST", - Network accessline 166
"url": "https://api.example.com/v1/apply", - Network accessline 166
"url": "https://api.example.com/v1/apply", - Network accessline 184
# Click a tab and wait for content nimble extract --url "https://example.com/product" --render \ - Network accessline 184
# Click a tab and wait for content nimble extract --url "https://example.com/product" --render \ - Network accessline 185
nimble extract --url "https://example.com/product" --render \ - Network accessline 185
nimble extract --url "https://example.com/product" --render \ - Network accessline 191
# Dismiss optional cookie banner, then extract nimble extract --url "https://example.com" --render \ - Network accessline 191
# Dismiss optional cookie banner, then extract nimble extract --url "https://example.com" --render \ - Network accessline 192
nimble extract --url "https://example.com" --render \ - Network accessline 192
nimble extract --url "https://example.com" --render \ - Network accessline 198
# Fill search form and submit nimble extract --url "https://example.com/search" --render \ - Network accessline 198
# Fill search form and submit nimble extract --url "https://example.com/search" --render \ - Network accessline 199
nimble extract --url "https://example.com/search" --render \ - Network accessline 199
nimble extract --url "https://example.com/search" --render \ - Network accessline 206
# Infinite scroll — load all lazy content nimble extract --url "https://example.com/feed" --render \ - Network accessline 206
# Infinite scroll — load all lazy content nimble extract --url "https://example.com/feed" --render \ - Network accessline 207
nimble extract --url "https://example.com/feed" --render \ - Network accessline 207
nimble extract --url "https://example.com/feed" --render \ - Network accessline 212
# Auto-scroll with "Load More" button nimble extract --url "https://example.com/products" --render \ - Network accessline 212
# Auto-scroll with "Load More" button nimble extract --url "https://example.com/products" --render \ - Network accessline 213
nimble extract --url "https://example.com/products" --render \ - Network accessline 213
nimble extract --url "https://example.com/products" --render \ - Network accessline 218
# Navigate to a tab URL, then extract nimble extract --url "https://example.com" --render \ - Network accessline 218
# Navigate to a tab URL, then extract nimble extract --url "https://example.com" --render \ - Network accessline 219
nimble extract --url "https://example.com" --render \ - Network accessline 219
nimble extract --url "https://example.com" --render \ - Network accessline 221
{"type": "goto", "url": "https://example.com/reviews"}, - Network accessline 221
{"type": "goto", "url": "https://example.com/reviews"}, - Network accessline 225
# Scroll to specific element nimble extract --url "https://example.com/page" --render \ - Network accessline 225
# Scroll to specific element nimble extract --url "https://example.com/page" --render \ - Network accessline 226
nimble extract --url "https://example.com/page" --render \ - Network accessline 226
nimble extract --url "https://example.com/page" --render \ - Network accessline 232
# Select dropdown then wait nimble extract --url "https://example.com/product" --render \ - Network accessline 232
# Select dropdown then wait nimble extract --url "https://example.com/product" --render \ - Network accessline 233
nimble extract --url "https://example.com/product" --render \ - Network accessline 233
nimble extract --url "https://example.com/product" --render \ - Network accessline 240
# Take screenshot for debugging nimble extract --url "https://example.com" --render \ - Network accessline 240
# Take screenshot for debugging nimble extract --url "https://example.com" --render \ - Network accessline 241
nimble extract --url "https://example.com" --render \ - Network accessline 241
nimble extract --url "https://example.com" --render \ - Network accessline 250
# Click a tab and wait for content resp = nimble.extract( url="https://example.com/product", - Network accessline 250
# Click a tab and wait for content resp = nimble.extract( url="https://example.com/product", - Network accessline 251
resp = nimble.extract( url="https://example.com/product", render=True, - Network accessline 251
resp = nimble.extract( url="https://example.com/product", render=True, - Network accessline 252
url="https://example.com/product", - Network accessline 252
url="https://example.com/product", - Network accessline 261
# Fill search form and submit resp = nimble.extract( url="https://example.com/search", - Network accessline 261
# Fill search form and submit resp = nimble.extract( url="https://example.com/search", - Network accessline 262
resp = nimble.extract( url="https://example.com/search", render=True, - Network accessline 262
resp = nimble.extract( url="https://example.com/search", render=True, - Network accessline 263
url="https://example.com/search", - Network accessline 263
url="https://example.com/search", - Network accessline 273
# Infinite scroll resp = nimble.extract( url="https://example.com/feed", - Network accessline 273
# Infinite scroll resp = nimble.extract( url="https://example.com/feed", - Network accessline 274
resp = nimble.extract( url="https://example.com/feed", render=True, - Network accessline 274
resp = nimble.extract( url="https://example.com/feed", render=True, - Network accessline 275
url="https://example.com/feed", - Network accessline 275
url="https://example.com/feed", - Network accessline 283
# Dismiss optional cookie banner then extract resp = nimble.extract( url="https://example.com", - Network accessline 283
# Dismiss optional cookie banner then extract resp = nimble.extract( url="https://example.com", - Network accessline 284
resp = nimble.extract( url="https://example.com", render=True, - Network accessline 284
resp = nimble.extract( url="https://example.com", render=True, - Network accessline 285
url="https://example.com", - Network accessline 285
url="https://example.com",
skills/nimble-web-expert/references/nimble-extract/browser-investigation.md
- Network accessline 37
[browser-use] Navigate to https://example.com/product - Network accessline 37
[browser-use] Navigate to https://example.com/product - Network accessline 49
browser = p.chromium.launch(headless=True) page = browser.new_page() page.goto("https://example.com/product") - Network accessline 49
browser = p.chromium.launch(headless=True) page = browser.new_page() page.goto("https://example.com/product") - Network accessline 50
page = browser.new_page() page.goto("https://example.com/product") page.wait_for_load_state("networkidle") - Network accessline 50
page = browser.new_page() page.goto("https://example.com/product") page.wait_for_load_state("networkidle") - Network accessline 51
page.goto("https://example.com/product") - Network accessline 51
page.goto("https://example.com/product") - Network accessline 67
nimble extract --url "https://example.com/product" --render --parse \ - Network accessline 67
nimble extract --url "https://example.com/product" --render --parse \ - Network accessline 84
[browser-use] Navigate to https://example.com/search?q=shoes [browser-use] Open DevTools Network tab, filter XHR/Fetch - Network accessline 84
[browser-use] Navigate to https://example.com/search?q=shoes [browser-use] Open DevTools Network tab, filter XHR/Fetch - Network accessline 98
api_calls = [] page.on("request", lambda req: api_calls.append(req) if req.resource_type in ("xhr", "fetch") else None) page.goto("https://example.com/search?q=shoes") - Network accessline 98
api_calls = [] page.on("request", lambda req: api_calls.append(req) if req.resource_type in ("xhr", "fetch") else None) page.goto("https://example.com/search?q=shoes") - Network accessline 99
page.on("request", lambda req: api_calls.append(req) if req.resource_type in ("xhr", "fetch") else None) page.goto("https://example.com/search?q=shoes") page.wait_for_timeout(5000) - Network accessline 99
page.on("request", lambda req: api_calls.append(req) if req.resource_type in ("xhr", "fetch") else None) page.goto("https://example.com/search?q=shoes") page.wait_for_timeout(5000) - Network accessline 100
page.goto("https://example.com/search?q=shoes") - Network accessline 100
page.goto("https://example.com/search?q=shoes") - Network accessline 110
# Option A — call the API directly (fastest, if no auth required) nimble --transform "data.markdown" extract \ --url "https://example.com/api/v2/search?q=shoes&page=1" \ - Network accessline 110
# Option A — call the API directly (fastest, if no auth required) nimble --transform "data.markdown" extract \ --url "https://example.com/api/v2/search?q=shoes&page=1" \ - Network accessline 111
nimble --transform "data.markdown" extract --url "https://example.com/api/v2/search?q=shoes&page=1" - Network accessline 111
nimble --transform "data.markdown" extract --url "https://example.com/api/v2/search?q=shoes&page=1" - Network accessline 112
--url "https://example.com/api/v2/search?q=shoes&page=1" \ - Network accessline 112
--url "https://example.com/api/v2/search?q=shoes&page=1" \ - Network accessline 115
[Credential-related source omitted] - Network accessline 115
[Credential-related source omitted] - Access to secretsline 115
[Credential-related source omitted] - Access to secretsline 115
[Credential-related source omitted] - Network accessline 116
nimble extract \ --url "https://example.com/search?q=shoes" --render \ --network-capture '[{"url": {"type": "contains", "value": "/api/v2/search"}, "resource_type": ["xhr", "fetch"]}]' \ - Network accessline 116
nimble extract \ --url "https://example.com/search?q=shoes" --render \ --network-capture '[{"url": {"type": "contains", "value": "/api/v2/search"}, "resource_type": ["xhr", "fetch"]}]' \ - Network accessline 117
--url "https://example.com/search?q=shoes" --render \ --network-capture '[{"url": {"type": "contains", "value": "/api/v2/search"}, "resource_type": ["xhr", "fetch"]}]' \ > .nimble/search-results.json - Network accessline 117
--url "https://example.com/search?q=shoes" --render \ --network-capture '[{"url": {"type": "contains", "value": "/api/v2/search"}, "resource_type": ["xhr", "fetch"]}]' \ > .nimble/search-results.json - Network accessline 129
[browser-use] Navigate to https://example.com/product - Network accessline 129
[browser-use] Navigate to https://example.com/product - Network accessline 141
browser = p.chromium.launch(headless=False) # headless=False to watch page = browser.new_page() page.goto("https://example.com/product") - Network accessline 141
browser = p.chromium.launch(headless=False) # headless=False to watch page = browser.new_page() page.goto("https://example.com/product") - Network accessline 142
page = browser.new_page() page.goto("https://example.com/product") page.wait_for_load_state("networkidle") - Network accessline 142
page = browser.new_page() page.goto("https://example.com/product") page.wait_for_load_state("networkidle") - Network accessline 143
page.goto("https://example.com/product") - Network accessline 143
page.goto("https://example.com/product") - Network accessline 155
nimble --transform "data.markdown" extract \ --url "https://example.com/product" --render \ - Network accessline 155
nimble --transform "data.markdown" extract \ --url "https://example.com/product" --render \ - Network accessline 156
--url "https://example.com/product" --render \ - Network accessline 156
--url "https://example.com/product" --render \
skills/nimble-web-expert/references/nimble-extract/network-capture.md
- Network accessline 12
Docs: https://docs.nimbleway.com/nimble-sdk/web-tools/extract/features/network-capture - Network accessline 12
Docs: https://docs.nimbleway.com/nimble-sdk/web-tools/extract/features/network-capture - Network accessline 47
nimble = Nimble() resp = nimble.extract( url="https://example.com/products", - Network accessline 47
nimble = Nimble() resp = nimble.extract( url="https://example.com/products", - Network accessline 48
resp = nimble.extract( url="https://example.com/products", render=True, - Network accessline 48
resp = nimble.extract( url="https://example.com/products", render=True, - Network accessline 49
url="https://example.com/products", render=True, network_capture=[{"url": {"type": "contains", "value": "/api/products"}, "resource_type": ["xhr", "fetch"]}], - Network accessline 49
url="https://example.com/products", render=True, network_capture=[{"url": {"type": "contains", "value": "/api/products"}, "resource_type": ["xhr", "fetch"]}], - Network accessline 74
# Capture a specific API endpoint by pattern nimble extract --url "https://example.com/products" --render \ - Network accessline 74
# Capture a specific API endpoint by pattern nimble extract --url "https://example.com/products" --render \ - Network accessline 75
nimble extract --url "https://example.com/products" --render \ - Network accessline 75
nimble extract --url "https://example.com/products" --render \ - Network accessline 79
# Narrow to XHR/fetch only nimble extract --url "https://example.com/products" --render \ - Network accessline 79
# Narrow to XHR/fetch only nimble extract --url "https://example.com/products" --render \ - Network accessline 80
nimble extract --url "https://example.com/products" --render \ - Network accessline 80
nimble extract --url "https://example.com/products" --render \ - Network accessline 86
# Capture exact endpoint nimble extract --url "https://example.com/page" --render \ - Network accessline 86
# Capture exact endpoint nimble extract --url "https://example.com/page" --render \ - Network accessline 87
nimble extract --url "https://example.com/page" --render \ - Network accessline 87
nimble extract --url "https://example.com/page" --render \ - Network accessline 88
--network-capture '[{"url": {"type": "exact", "value": "https://example.com/api/v2/listings"}}]' \ - Network accessline 88
--network-capture '[{"url": {"type": "exact", "value": "https://example.com/api/v2/listings"}}]' \ - Network accessline 91
# Wait for 3 matching requests (pagination / multiple chunks) nimble extract --url "https://example.com/feed" --render \ - Network accessline 91
# Wait for 3 matching requests (pagination / multiple chunks) nimble extract --url "https://example.com/feed" --render \ - Network accessline 92
nimble extract --url "https://example.com/feed" --render \ - Network accessline 92
nimble extract --url "https://example.com/feed" --render \ - Network accessline 99
# Capture multiple endpoints simultaneously nimble extract --url "https://example.com/page" --render \ - Network accessline 99
# Capture multiple endpoints simultaneously nimble extract --url "https://example.com/page" --render \ - Network accessline 100
nimble extract --url "https://example.com/page" --render \ - Network accessline 100
nimble extract --url "https://example.com/page" --render \ - Network accessline 106
# Capture POST requests triggered by a form fill nimble extract --url "https://example.com/search" --render \ - Network accessline 106
# Capture POST requests triggered by a form fill nimble extract --url "https://example.com/search" --render \ - Network accessline 107
nimble extract --url "https://example.com/search" --render \ - Network accessline 107
nimble extract --url "https://example.com/search" --render \ - Network accessline 121
nimble extract --url "https://example.com/products" --render \ - Network accessline 121
nimble extract --url "https://example.com/products" --render \ - Network accessline 140
Docs: https://docs.nimbleway.com/nimble-sdk/web-tools/extract/features/network-capture#xhr-without-rendering - Network accessline 140
Docs: https://docs.nimbleway.com/nimble-sdk/web-tools/extract/features/network-capture#xhr-without-rendering - Network accessline 151
# GET request to a public API nimble extract --url "https://api.example.com/v1/markets?q=elections&limit=50" \ - Network accessline 151
# GET request to a public API nimble extract --url "https://api.example.com/v1/markets?q=elections&limit=50" \ - Network accessline 152
nimble extract --url "https://api.example.com/v1/markets?q=elections&limit=50" \ - Network accessline 152
nimble extract --url "https://api.example.com/v1/markets?q=elections&limit=50" \ - Network accessline 155
# POST request nimble extract --url "https://api.example.com/v1/search" \ - Network accessline 155
# POST request nimble extract --url "https://api.example.com/v1/search" \ - Network accessline 156
nimble extract --url "https://api.example.com/v1/search" \ - Network accessline 156
nimble extract --url "https://api.example.com/v1/search" \ - Network accessline 165
# GET — direct API endpoint resp = nimble.extract( url="https://api.example.com/v1/markets?q=elections&limit=50", - Network accessline 165
# GET — direct API endpoint resp = nimble.extract( url="https://api.example.com/v1/markets?q=elections&limit=50", - Network accessline 166
resp = nimble.extract( url="https://api.example.com/v1/markets?q=elections&limit=50", is_xhr=True, - Network accessline 166
resp = nimble.extract( url="https://api.example.com/v1/markets?q=elections&limit=50", is_xhr=True, - Network accessline 167
url="https://api.example.com/v1/markets?q=elections&limit=50", - Network accessline 167
url="https://api.example.com/v1/markets?q=elections&limit=50", - Network accessline 172
# POST resp = nimble.extract( url="https://api.example.com/v1/search", - Network accessline 172
# POST resp = nimble.extract( url="https://api.example.com/v1/search", - Network accessline 173
resp = nimble.extract( url="https://api.example.com/v1/search", method="POST", - Network accessline 173
resp = nimble.extract( url="https://api.example.com/v1/search", method="POST", - Network accessline 174
url="https://api.example.com/v1/search", - Network accessline 174
url="https://api.example.com/v1/search", - Network accessline 183
# Polymarket — search markets by keyword nimble extract --url "https://gamma-api.polymarket.com/markets?_q=elections&limit=50&active=true" \ - Network accessline 183
# Polymarket — search markets by keyword nimble extract --url "https://gamma-api.polymarket.com/markets?_q=elections&limit=50&active=true" \ - Network accessline 184
nimble extract --url "https://gamma-api.polymarket.com/markets?_q=elections&limit=50&active=true" \ - Network accessline 184
nimble extract --url "https://gamma-api.polymarket.com/markets?_q=elections&limit=50&active=true" \ - Network accessline 187
# Any public JSON API nimble extract --url "https://api.example.com/products?category=laptops&limit=20" \ - Network accessline 187
# Any public JSON API nimble extract --url "https://api.example.com/products?category=laptops&limit=20" \ - Network accessline 188
nimble extract --url "https://api.example.com/products?category=laptops&limit=20" \ - Network accessline 188
nimble extract --url "https://api.example.com/products?category=laptops&limit=20" \ - Network accessline 191
# API requiring a specific HTTP method nimble extract --url "https://api.example.com/v2/search" \ - Network accessline 191
# API requiring a specific HTTP method nimble extract --url "https://api.example.com/v2/search" \ - Network accessline 192
nimble extract --url "https://api.example.com/v2/search" \ - Network accessline 192
nimble extract --url "https://api.example.com/v2/search" \
skills/nimble-web-expert/references/nimble-extract/parsing-schema.md
- Network accessline 11
Docs: https://docs.nimbleway.com/nimble-sdk/web-tools/extract/features/parsing-schema - Network accessline 11
Docs: https://docs.nimbleway.com/nimble-sdk/web-tools/extract/features/parsing-schema - Network accessline 43
nimble = Nimble() resp = nimble.extract( url="https://example.com/product", - Network accessline 43
nimble = Nimble() resp = nimble.extract( url="https://example.com/product", - Network accessline 44
resp = nimble.extract( url="https://example.com/product", render=True, - Network accessline 44
resp = nimble.extract( url="https://example.com/product", render=True, - Network accessline 45
url="https://example.com/product", - Network accessline 45
url="https://example.com/product", - Network accessline 122
# Single product — extract specific fields nimble extract --url "https://example.com/product/123" --parse \ - Network accessline 122
# Single product — extract specific fields nimble extract --url "https://example.com/product/123" --parse \ - Network accessline 123
nimble extract --url "https://example.com/product/123" --parse \ - Network accessline 123
nimble extract --url "https://example.com/product/123" --parse \ - Network accessline 133
# List of products from search results nimble extract --url "https://example.com/search?q=shoes" --parse \ - Network accessline 133
# List of products from search results nimble extract --url "https://example.com/search?q=shoes" --parse \ - Network accessline 134
nimble extract --url "https://example.com/search?q=shoes" --parse \ - Network accessline 134
nimble extract --url "https://example.com/search?q=shoes" --parse \ - Network accessline 145
# Fallback — try two selectors, use first that works nimble extract --url "https://example.com/product" --parse \ - Network accessline 145
# Fallback — try two selectors, use first that works nimble extract --url "https://example.com/product" --parse \ - Network accessline 146
nimble extract --url "https://example.com/product" --parse \ - Network accessline 146
nimble extract --url "https://example.com/product" --parse \ - Network accessline 156
# Extract all image URLs as a list nimble extract --url "https://example.com/product" --parse \ - Network accessline 156
# Extract all image URLs as a list nimble extract --url "https://example.com/product" --parse \ - Network accessline 157
nimble extract --url "https://example.com/product" --parse \ - Network accessline 157
nimble extract --url "https://example.com/product" --parse \ - Network accessline 164
# Extract embedded JSON-LD (schema.org) nimble extract --url "https://example.com/product" --parse \ - Network accessline 164
# Extract embedded JSON-LD (schema.org) nimble extract --url "https://example.com/product" --parse \ - Network accessline 165
nimble extract --url "https://example.com/product" --parse \ - Network accessline 165
nimble extract --url "https://example.com/product" --parse \ - Network accessline 175
# Parse RSS feed with XPath nimble extract --url "https://example.com/feed.xml" --parse \ - Network accessline 175
# Parse RSS feed with XPath nimble extract --url "https://example.com/feed.xml" --parse \ - Network accessline 176
nimble extract --url "https://example.com/feed.xml" --parse \ - Network accessline 176
nimble extract --url "https://example.com/feed.xml" --parse \ - Network accessline 187
# Extract data from network capture response nimble extract --url "https://example.com/products" --render \ - Network accessline 187
# Extract data from network capture response nimble extract --url "https://example.com/products" --render \ - Network accessline 188
nimble extract --url "https://example.com/products" --render \ - Network accessline 188
nimble extract --url "https://example.com/products" --render \ - Network accessline 203
# Single product resp = nimble.extract( url="https://example.com/product/123", - Network accessline 203
# Single product resp = nimble.extract( url="https://example.com/product/123", - Network accessline 204
resp = nimble.extract( url="https://example.com/product/123", parse=True, - Network accessline 204
resp = nimble.extract( url="https://example.com/product/123", parse=True, - Network accessline 205
url="https://example.com/product/123", - Network accessline 205
url="https://example.com/product/123", - Network accessline 218
# List of products from search results resp = nimble.extract( url="https://example.com/search?q=shoes", - Network accessline 218
# List of products from search results resp = nimble.extract( url="https://example.com/search?q=shoes", - Network accessline 219
resp = nimble.extract( url="https://example.com/search?q=shoes", parse=True, - Network accessline 219
resp = nimble.extract( url="https://example.com/search?q=shoes", parse=True, - Network accessline 220
url="https://example.com/search?q=shoes", - Network accessline 220
url="https://example.com/search?q=shoes", - Network accessline 235
# All image URLs as a list resp = nimble.extract( url="https://example.com/product", - Network accessline 235
# All image URLs as a list resp = nimble.extract( url="https://example.com/product", - Network accessline 236
resp = nimble.extract( url="https://example.com/product", parse=True, - Network accessline 236
resp = nimble.extract( url="https://example.com/product", parse=True, - Network accessline 237
url="https://example.com/product", - Network accessline 237
url="https://example.com/product",
skills/nimble-web-expert/references/nimble-extract/reference.md
- Network accessline 68
# Markdown output (default for most tasks) nimble --transform "data.markdown" extract \ --url "https://example.com/page" --format markdown - Network accessline 68
# Markdown output (default for most tasks) nimble --transform "data.markdown" extract \ --url "https://example.com/page" --format markdown - Network accessline 69
nimble --transform "data.markdown" extract --url "https://example.com/page" --format markdown - Network accessline 69
nimble --transform "data.markdown" extract --url "https://example.com/page" --format markdown - Network accessline 70
--url "https://example.com/page" --format markdown - Network accessline 70
--url "https://example.com/page" --format markdown - Network accessline 72
# Save to file nimble --transform "data.markdown" extract \ --url "https://example.com/page" --format markdown > .nimble/page.md - Network accessline 72
# Save to file nimble --transform "data.markdown" extract \ --url "https://example.com/page" --format markdown > .nimble/page.md - Network accessline 73
nimble --transform "data.markdown" extract --url "https://example.com/page" --format markdown > .nimble/page.md - Network accessline 73
nimble --transform "data.markdown" extract --url "https://example.com/page" --format markdown > .nimble/page.md - Network accessline 74
--url "https://example.com/page" --format markdown > .nimble/page.md - Network accessline 74
--url "https://example.com/page" --format markdown > .nimble/page.md - Network accessline 82
nimble = Nimble() resp = nimble.extract(url="https://example.com/page", formats=["markdown"]) - Network accessline 82
nimble = Nimble() resp = nimble.extract(url="https://example.com/page", formats=["markdown"]) - Network accessline 83
resp = nimble.extract(url="https://example.com/page", formats=["markdown"]) - Network accessline 83
resp = nimble.extract(url="https://example.com/page", formats=["markdown"]) - Network accessline 103
# Tier 1 — no render nimble --transform "data.markdown" extract --url "https://example.com" --format markdown - Network accessline 103
# Tier 1 — no render nimble --transform "data.markdown" extract --url "https://example.com" --format markdown - Network accessline 104
nimble --transform "data.markdown" extract --url "https://example.com" --format markdown - Network accessline 104
nimble --transform "data.markdown" extract --url "https://example.com" --format markdown - Network accessline 106
# Tier 2 — render nimble --transform "data.markdown" extract --url "https://example.com" --render --format markdown - Network accessline 106
# Tier 2 — render nimble --transform "data.markdown" extract --url "https://example.com" --render --format markdown - Network accessline 107
nimble --transform "data.markdown" extract --url "https://example.com" --render --format markdown - Network accessline 107
nimble --transform "data.markdown" extract --url "https://example.com" --render --format markdown - Network accessline 109
# Tier 3 — full browser profile nimble --transform "data.markdown" extract --url "https://example.com" --render --driver vx10-pro --format markdown - Network accessline 109
# Tier 3 — full browser profile nimble --transform "data.markdown" extract --url "https://example.com" --render --driver vx10-pro --format markdown - Network accessline 110
nimble --transform "data.markdown" extract --url "https://example.com" --render --driver vx10-pro --format markdown - Network accessline 110
nimble --transform "data.markdown" extract --url "https://example.com" --render --driver vx10-pro --format markdown - Network accessline 114
# Tier 2 — render resp = nimble.extract(url="https://example.com", render=True, formats=["markdown"]) - Network accessline 114
# Tier 2 — render resp = nimble.extract(url="https://example.com", render=True, formats=["markdown"]) - Network accessline 115
resp = nimble.extract(url="https://example.com", render=True, formats=["markdown"]) - Network accessline 115
resp = nimble.extract(url="https://example.com", render=True, formats=["markdown"]) - Network accessline 117
# Tier 3 — full browser profile resp = nimble.extract(url="https://example.com", render=True, driver="vx10-pro", formats=["markdown"]) - Network accessline 117
# Tier 3 — full browser profile resp = nimble.extract(url="https://example.com", render=True, driver="vx10-pro", formats=["markdown"]) - Network accessline 118
resp = nimble.extract(url="https://example.com", render=True, driver="vx10-pro", formats=["markdown"]) - Network accessline 118
resp = nimble.extract(url="https://example.com", render=True, driver="vx10-pro", formats=["markdown"]) - Network accessline 130
nimble --transform "data.markdown" extract \ --url "https://example.com/product" --render \ - Network accessline 130
nimble --transform "data.markdown" extract \ --url "https://example.com/product" --render \ - Network accessline 131
--url "https://example.com/product" --render \ - Network accessline 131
--url "https://example.com/product" --render \ - Network accessline 139
resp = nimble.extract( url="https://example.com/product", - Network accessline 139
resp = nimble.extract( url="https://example.com/product", - Network accessline 140
url="https://example.com/product", - Network accessline 140
url="https://example.com/product", - Network accessline 159
# Intercept an API call triggered by the page nimble extract \ --url "https://example.com/products" --render \ - Network accessline 159
# Intercept an API call triggered by the page nimble extract \ --url "https://example.com/products" --render \ - Network accessline 160
nimble extract \ --url "https://example.com/products" --render \ --network-capture '[{"url": {"type": "contains", "value": "/api/products"}, "resource_type": ["xhr", "fetch"]}]' \ - Network accessline 160
nimble extract \ --url "https://example.com/products" --render \ --network-capture '[{"url": {"type": "contains", "value": "/api/products"}, "resource_type": ["xhr", "fetch"]}]' \ - Network accessline 161
--url "https://example.com/products" --render \ --network-capture '[{"url": {"type": "contains", "value": "/api/products"}, "resource_type": ["xhr", "fetch"]}]' \ > .nimble/products-api.json - Network accessline 161
--url "https://example.com/products" --render \ --network-capture '[{"url": {"type": "contains", "value": "/api/products"}, "resource_type": ["xhr", "fetch"]}]' \ > .nimble/products-api.json - Network accessline 165
# Known public API endpoint — use --is-xhr (no browser, fastest) nimble --transform "data.markdown" extract \ --url "https://api.example.com/v1/markets?q=elections&limit=50" \ - Network accessline 165
# Known public API endpoint — use --is-xhr (no browser, fastest) nimble --transform "data.markdown" extract \ --url "https://api.example.com/v1/markets?q=elections&limit=50" \ - Network accessline 166
nimble --transform "data.markdown" extract --url "https://api.example.com/v1/markets?q=elections&limit=50" - Network accessline 166
nimble --transform "data.markdown" extract --url "https://api.example.com/v1/markets?q=elections&limit=50" - Network accessline 167
--url "https://api.example.com/v1/markets?q=elections&limit=50" \ - Network accessline 167
--url "https://api.example.com/v1/markets?q=elections&limit=50" \ - Network accessline 172
# Intercept via render resp = nimble.extract( url="https://example.com/products", - Network accessline 172
# Intercept via render resp = nimble.extract( url="https://example.com/products", - Network accessline 173
resp = nimble.extract( url="https://example.com/products", render=True, - Network accessline 173
resp = nimble.extract( url="https://example.com/products", render=True, - Network accessline 174
url="https://example.com/products", render=True, network_capture=[{"url": {"type": "contains", "value": "/api/products"}, "resource_type": ["xhr", "fetch"]}], - Network accessline 174
url="https://example.com/products", render=True, network_capture=[{"url": {"type": "contains", "value": "/api/products"}, "resource_type": ["xhr", "fetch"]}], - Network accessline 180
# Direct API call — no browser resp = nimble.extract( url="https://api.example.com/v1/markets?q=elections&limit=50", - Network accessline 180
# Direct API call — no browser resp = nimble.extract( url="https://api.example.com/v1/markets?q=elections&limit=50", - Network accessline 181
resp = nimble.extract( url="https://api.example.com/v1/markets?q=elections&limit=50", is_xhr=True, - Network accessline 181
resp = nimble.extract( url="https://api.example.com/v1/markets?q=elections&limit=50", is_xhr=True, - Network accessline 182
url="https://api.example.com/v1/markets?q=elections&limit=50", - Network accessline 182
url="https://api.example.com/v1/markets?q=elections&limit=50", - Network accessline 198
nimble extract --url "https://example.com/product" --render --parse \ - Network accessline 198
nimble extract --url "https://example.com/product" --render --parse \ - Network accessline 209
resp = nimble.extract( url="https://example.com/product", - Network accessline 209
resp = nimble.extract( url="https://example.com/product", - Network accessline 210
url="https://example.com/product", - Network accessline 210
url="https://example.com/product", - Network accessline 229
# Country nimble --transform "data.markdown" extract --url "https://example.com" --country US --format markdown - Network accessline 229
# Country nimble --transform "data.markdown" extract --url "https://example.com" --country US --format markdown - Network accessline 230
nimble --transform "data.markdown" extract --url "https://example.com" --country US --format markdown - Network accessline 230
nimble --transform "data.markdown" extract --url "https://example.com" --country US --format markdown - Network accessline 232
# City-level nimble --transform "data.markdown" extract --url "https://example.com" --country US --state CA --city los_angeles --format markdown - Network accessline 232
# City-level nimble --transform "data.markdown" extract --url "https://example.com" --country US --state CA --city los_angeles --format markdown - Network accessline 233
nimble --transform "data.markdown" extract --url "https://example.com" --country US --state CA --city los_angeles --format markdown - Network accessline 233
nimble --transform "data.markdown" extract --url "https://example.com" --country US --state CA --city los_angeles --format markdown - Network accessline 235
# Localized (pair --locale with --country) nimble --transform "data.markdown" extract --url "https://example.com/fr" --country FR --locale fr-FR --format markdown - Network accessline 235
# Localized (pair --locale with --country) nimble --transform "data.markdown" extract --url "https://example.com/fr" --country FR --locale fr-FR --format markdown - Network accessline 236
nimble --transform "data.markdown" extract --url "https://example.com/fr" --country FR --locale fr-FR --format markdown - Network accessline 236
nimble --transform "data.markdown" extract --url "https://example.com/fr" --country FR --locale fr-FR --format markdown - Network accessline 240
resp = nimble.extract(url="https://example.com", country="US", formats=["markdown"]) - Network accessline 240
resp = nimble.extract(url="https://example.com", country="US", formats=["markdown"]) - Network accessline 242
resp = nimble.extract(url="https://example.com", country="US", state="CA", city="los_angeles", formats=["markdown"]) - Network accessline 242
resp = nimble.extract(url="https://example.com", country="US", state="CA", city="los_angeles", formats=["markdown"]) - Network accessline 264
# Submit async nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 264
# Submit async nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 265
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 265
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 278
async def extract(): nimble = AsyncNimble() task = await nimble.extract_async(url="https://example.com/page", render=True, formats=["markdown"]) - Network accessline 278
async def extract(): nimble = AsyncNimble() task = await nimble.extract_async(url="https://example.com/page", render=True, formats=["markdown"]) - Network accessline 279
nimble = AsyncNimble() task = await nimble.extract_async(url="https://example.com/page", render=True, formats=["markdown"]) task_id = task["task"]["id"] - Network accessline 279
nimble = AsyncNimble() task = await nimble.extract_async(url="https://example.com/page", render=True, formats=["markdown"]) task_id = task["task"]["id"] - Network accessline 280
task = await nimble.extract_async(url="https://example.com/page", render=True, formats=["markdown"]) - Network accessline 280
task = await nimble.extract_async(url="https://example.com/page", render=True, formats=["markdown"]) - Network accessline 316
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 316
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 317
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' \ - Network accessline 317
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' \ - Network accessline 318
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 318
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 319
--input '{"url": "https://example.com/page-2"}' \ - Network accessline 319
--input '{"url": "https://example.com/page-2"}' \ - Network accessline 320
--input '{"url": "https://example.com/page-3"}' - Network accessline 320
--input '{"url": "https://example.com/page-3"}' - Network accessline 326
resp = nimble.extract_batch( inputs=[ {"url": "https://example.com/page-1"}, - Network accessline 326
resp = nimble.extract_batch( inputs=[ {"url": "https://example.com/page-1"}, - Network accessline 327
inputs=[ {"url": "https://example.com/page-1"}, {"url": "https://example.com/page-2"}, - Network accessline 327
inputs=[ {"url": "https://example.com/page-1"}, {"url": "https://example.com/page-2"}, - Network accessline 328
{"url": "https://example.com/page-1"}, - Network accessline 328
{"url": "https://example.com/page-1"}, - Network accessline 329
{"url": "https://example.com/page-2"}, - Network accessline 329
{"url": "https://example.com/page-2"}, - Network accessline 330
{"url": "https://example.com/page-3"}, - Network accessline 330
{"url": "https://example.com/page-3"}, - Network accessline 340
const resp = await nimble.extractBatch({ inputs: [ { url: "https://example.com/page-1" }, - Network accessline 340
const resp = await nimble.extractBatch({ inputs: [ { url: "https://example.com/page-1" }, - Network accessline 341
inputs: [ { url: "https://example.com/page-1" }, { url: "https://example.com/page-2" }, - Network accessline 341
inputs: [ { url: "https://example.com/page-1" }, { url: "https://example.com/page-2" }, - Network accessline 342
{ url: "https://example.com/page-1" }, - Network accessline 342
{ url: "https://example.com/page-1" }, - Network accessline 343
{ url: "https://example.com/page-2" }, - Network accessline 343
{ url: "https://example.com/page-2" }, - Network accessline 344
{ url: "https://example.com/page-3" }, - Network accessline 344
{ url: "https://example.com/page-3" }, - Network accessline 378
mkdir -p .nimble nimble --transform "data.markdown" extract --url "https://example.com/1" --format markdown > .nimble/1.md & - Network accessline 378
mkdir -p .nimble nimble --transform "data.markdown" extract --url "https://example.com/1" --format markdown > .nimble/1.md & - Network accessline 379
nimble --transform "data.markdown" extract --url "https://example.com/1" --format markdown > .nimble/1.md & - Network accessline 379
nimble --transform "data.markdown" extract --url "https://example.com/1" --format markdown > .nimble/1.md & - Network accessline 380
nimble --transform "data.markdown" extract --url "https://example.com/2" --format markdown > .nimble/2.md & - Network accessline 380
nimble --transform "data.markdown" extract --url "https://example.com/2" --format markdown > .nimble/2.md & - Network accessline 381
nimble --transform "data.markdown" extract --url "https://example.com/3" --format markdown > .nimble/3.md & - Network accessline 381
nimble --transform "data.markdown" extract --url "https://example.com/3" --format markdown > .nimble/3.md &
skills/nimble-web-expert/references/nimble-map/reference.md
- Network accessline 38
nimble map --url "https://docs.example.com" --limit 100 - Network accessline 38
nimble map --url "https://docs.example.com" --limit 100 - Network accessline 40
# Sitemap only (fastest) nimble map --url "https://example.com" --sitemap only --limit 500 - Network accessline 40
# Sitemap only (fastest) nimble map --url "https://example.com" --sitemap only --limit 500 - Network accessline 41
nimble map --url "https://example.com" --sitemap only --limit 500 - Network accessline 41
nimble map --url "https://example.com" --sitemap only --limit 500 - Network accessline 43
# Extract just the URL list nimble --transform "links.#.url" map --url "https://docs.example.com" --limit 100 - Network accessline 43
# Extract just the URL list nimble --transform "links.#.url" map --url "https://docs.example.com" --limit 100 - Network accessline 44
nimble --transform "links.#.url" map --url "https://docs.example.com" --limit 100 - Network accessline 44
nimble --transform "links.#.url" map --url "https://docs.example.com" --limit 100 - Access to secretsline 51
[Credential-related source omitted] - Access to secretsline 51
[Credential-related source omitted] - Network accessline 53
resp = nimble.map(url="https://docs.example.com", limit=100, sitemap="include") - Network accessline 53
resp = nimble.map(url="https://docs.example.com", limit=100, sitemap="include") - Network accessline 74
# Map → filter → extract nimble --transform "links.#.url" map --url "https://docs.stripe.com" --limit 200 > .nimble/urls.txt - Network accessline 74
# Map → filter → extract nimble --transform "links.#.url" map --url "https://docs.stripe.com" --limit 200 > .nimble/urls.txt - Network accessline 75
nimble --transform "links.#.url" map --url "https://docs.stripe.com" --limit 200 > .nimble/urls.txt - Network accessline 75
nimble --transform "links.#.url" map --url "https://docs.stripe.com" --limit 200 > .nimble/urls.txt - Network accessline 78
# Specific path section nimble map --url "https://shop.example.com/products/" --limit 200 - Network accessline 78
# Specific path section nimble map --url "https://shop.example.com/products/" --limit 200 - Network accessline 79
nimble map --url "https://shop.example.com/products/" --limit 200 - Network accessline 79
nimble map --url "https://shop.example.com/products/" --limit 200
skills/nimble-web-expert/references/nimble-search/reference.md
skills/nimble-web-expert/references/nimble-tasks/reference.md
skills/nimble-web-expert/references/recipes.md
- Network accessline 17
mkdir -p .nimble nimble --transform "data.markdown" extract \ --url "https://example.com/any-page" --format markdown > .nimble/page.md - Network accessline 17
mkdir -p .nimble nimble --transform "data.markdown" extract \ --url "https://example.com/any-page" --format markdown > .nimble/page.md - Network accessline 18
nimble --transform "data.markdown" extract --url "https://example.com/any-page" --format markdown > .nimble/page.md - Network accessline 18
nimble --transform "data.markdown" extract --url "https://example.com/any-page" --format markdown > .nimble/page.md - Network accessline 19
--url "https://example.com/any-page" --format markdown > .nimble/page.md - Network accessline 19
--url "https://example.com/any-page" --format markdown > .nimble/page.md - Network accessline 48
nimble extract --url "https://www.amazon.com/dp/B0CHWRXH8B" --country US --parse \ - Network accessline 48
nimble extract --url "https://www.amazon.com/dp/B0CHWRXH8B" --country US --parse \ - Network accessline 79
nimble extract \ --url "https://www.yelp.com/search?find_desc=italian+restaurant&find_loc=San+Francisco%2C+CA" \ - Network accessline 79
nimble extract \ --url "https://www.yelp.com/search?find_desc=italian+restaurant&find_loc=San+Francisco%2C+CA" \ - Network accessline 80
--url "https://www.yelp.com/search?find_desc=italian+restaurant&find_loc=San+Francisco%2C+CA" \ - Network accessline 80
--url "https://www.yelp.com/search?find_desc=italian+restaurant&find_loc=San+Francisco%2C+CA" \ - Network accessline 104
nimble extract \ --url "https://www.target.com/p/-/A-88790928" \ - Network accessline 104
nimble extract \ --url "https://www.target.com/p/-/A-88790928" \ - Network accessline 105
--url "https://www.target.com/p/-/A-88790928" \ - Network accessline 105
--url "https://www.target.com/p/-/A-88790928" \ - Network accessline 123
# Polymarket nimble --transform "data.markdown" extract \ --url "https://gamma-api.polymarket.com/markets?_q=elections&limit=20&active=true" \ - Network accessline 123
# Polymarket nimble --transform "data.markdown" extract \ --url "https://gamma-api.polymarket.com/markets?_q=elections&limit=20&active=true" \ - Network accessline 124
nimble --transform "data.markdown" extract --url "https://gamma-api.polymarket.com/markets?_q=elections&limit=20&active=true" - Network accessline 124
nimble --transform "data.markdown" extract --url "https://gamma-api.polymarket.com/markets?_q=elections&limit=20&active=true" - Network accessline 125
--url "https://gamma-api.polymarket.com/markets?_q=elections&limit=20&active=true" \ - Network accessline 125
--url "https://gamma-api.polymarket.com/markets?_q=elections&limit=20&active=true" \ - Network accessline 128
# Any known JSON API nimble --transform "data.markdown" extract \ --url "https://api.example.com/v1/endpoint?param=value" \ - Network accessline 128
# Any known JSON API nimble --transform "data.markdown" extract \ --url "https://api.example.com/v1/endpoint?param=value" \ - Network accessline 129
nimble --transform "data.markdown" extract --url "https://api.example.com/v1/endpoint?param=value" - Network accessline 129
nimble --transform "data.markdown" extract --url "https://api.example.com/v1/endpoint?param=value" - Network accessline 130
--url "https://api.example.com/v1/endpoint?param=value" \ - Network accessline 130
--url "https://api.example.com/v1/endpoint?param=value" \ - Network accessline 139
nimble --transform "data.markdown" extract \ --url "https://react.dev/reference/rsc/server-components" --format markdown > .nimble/react-docs.md - Network accessline 139
nimble --transform "data.markdown" extract \ --url "https://react.dev/reference/rsc/server-components" --format markdown > .nimble/react-docs.md - Network accessline 140
--url "https://react.dev/reference/rsc/server-components" --format markdown > .nimble/react-docs.md - Network accessline 140
--url "https://react.dev/reference/rsc/server-components" --format markdown > .nimble/react-docs.md - Network accessline 149
nimble --transform "data.markdown" extract \ --url "https://www.linkedin.com/jobs/search/?keywords=data+scientist&location=Austin%2C+TX&f_TPR=r604800" \ - Network accessline 149
nimble --transform "data.markdown" extract \ --url "https://www.linkedin.com/jobs/search/?keywords=data+scientist&location=Austin%2C+TX&f_TPR=r604800" \ - Network accessline 150
--url "https://www.linkedin.com/jobs/search/?keywords=data+scientist&location=Austin%2C+TX&f_TPR=r604800" \ - Network accessline 150
--url "https://www.linkedin.com/jobs/search/?keywords=data+scientist&location=Austin%2C+TX&f_TPR=r604800" \ - Network accessline 177
# Search → extract top results nimble search --query "React server components best practices" --focus coding --search-depth lite --include-answer nimble --transform "data.markdown" extract --url "https://react.dev/reference/rsc/server-compo - Network accessline 177
# Search → extract top results nimble search --query "React server components best practices" --focus coding --search-depth lite --include-answer nimble --transform "data.markdown" extract --url "https://react.dev/reference/rsc/server-compo - Network accessline 179
nimble --transform "data.markdown" extract --url "https://react.dev/reference/rsc/server-components" --format markdown - Network accessline 179
nimble --transform "data.markdown" extract --url "https://react.dev/reference/rsc/server-components" --format markdown - Network accessline 187
nimble --transform "links.#.url" map --url "https://docs.stripe.com" --limit 200 > .nimble/stripe-urls.txt - Network accessline 187
nimble --transform "links.#.url" map --url "https://docs.stripe.com" --limit 200 > .nimble/stripe-urls.txt - Network accessline 189
nimble --transform "data.markdown" extract --url "https://docs.stripe.com/api/charges/object" --format markdown - Network accessline 189
nimble --transform "data.markdown" extract --url "https://docs.stripe.com/api/charges/object" --format markdown
skills/nimble-web-expert/rules/setup.md
- Network accessline 24
The Nimble plugin includes a `.mcp.json` that auto-registers as a Connector pointing at `https://mcp.nimbleway.com/mcp` over native HTTP with OAuth. After - Network accessline 24
The Nimble plugin includes a `.mcp.json` that auto-registers as a Connector pointing at `https://mcp.nimbleway.com/mcp` over native HTTP with OAuth. After - Network accessline 25
pointing at `https://mcp.nimbleway.com/mcp` over native HTTP with OAuth. After - Network accessline 25
pointing at `https://mcp.nimbleway.com/mcp` over native HTTP with OAuth. After - Network accessline 38
Expect: `plugin:nimble:nimble: https://mcp.nimbleway.com/mcp (HTTP) - ✓ Connected` - Network accessline 38
Expect: `plugin:nimble:nimble: https://mcp.nimbleway.com/mcp (HTTP) - ✓ Connected` - Access to secretsline 96
[Credential-related source omitted] - Access to secretsline 96
[Credential-related source omitted] - Access to secretsline 97
[Credential-related source omitted] - Access to secretsline 97
[Credential-related source omitted] - Access to secretsline 98
[Credential-related source omitted] - Access to secretsline 98
[Credential-related source omitted] - Access to secretsline 99
[Credential-related source omitted] - Access to secretsline 99
[Credential-related source omitted] - Access to secretsline 100
[Credential-related source omitted] - Access to secretsline 100
[Credential-related source omitted] - Network accessline 127
open -a "Google Chrome" "https://online.nimbleway.com/overview" 2>/dev/null || open "https://online.nimbleway.com/overview" - Network accessline 127
open -a "Google Chrome" "https://online.nimbleway.com/overview" 2>/dev/null || open "https://online.nimbleway.com/overview" - Access to secretsline 137
[Credential-related source omitted] - Access to secretsline 137
[Credential-related source omitted] - Access to secretsline 143
[Credential-related source omitted] - Access to secretsline 143
[Credential-related source omitted] - Access to secretsline 149
[Credential-related source omitted] - Access to secretsline 149
[Credential-related source omitted] - Network accessline 160
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 160
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 161
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 161
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 162
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 162
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"args": [ "-y", "mcp-remote@latest", "https://mcp.nimbleway.com/mcp", - Network accessline 176
"args": [ "-y", "mcp-remote@latest", "https://mcp.nimbleway.com/mcp", - Network accessline 177
[Credential-related source omitted] - Network accessline 177
[Credential-related source omitted] - Network accessline 178
"https://mcp.nimbleway.com/mcp", - Network accessline 178
"https://mcp.nimbleway.com/mcp", - Access to secretsline 179
[Credential-related source omitted] - Access to secretsline 179
[Credential-related source omitted] - Network accessline 195
claude mcp add --transport http nimble-docs https://docs.nimbleway.com/mcp - Network accessline 195
claude mcp add --transport http nimble-docs https://docs.nimbleway.com/mcp - Network accessline 203
# Compact overview nimble --transform "data.markdown" extract \ --url "https://docs.nimbleway.com/llms.txt" --format markdown - Network accessline 203
# Compact overview nimble --transform "data.markdown" extract \ --url "https://docs.nimbleway.com/llms.txt" --format markdown - Network accessline 204
nimble --transform "data.markdown" extract --url "https://docs.nimbleway.com/llms.txt" --format markdown - Network accessline 204
nimble --transform "data.markdown" extract --url "https://docs.nimbleway.com/llms.txt" --format markdown - Network accessline 205
--url "https://docs.nimbleway.com/llms.txt" --format markdown - Network accessline 205
--url "https://docs.nimbleway.com/llms.txt" --format markdown - Network accessline 207
# Full documentation nimble --transform "data.markdown" extract \ --url "https://docs.nimbleway.com/llms-full.txt" --format markdown > .nimble/nimble-docs-full.md - Network accessline 207
# Full documentation nimble --transform "data.markdown" extract \ --url "https://docs.nimbleway.com/llms-full.txt" --format markdown > .nimble/nimble-docs-full.md - Network accessline 208
nimble --transform "data.markdown" extract --url "https://docs.nimbleway.com/llms-full.txt" --format markdown > .nimble/nimble-docs-full.md - Network accessline 208
nimble --transform "data.markdown" extract --url "https://docs.nimbleway.com/llms-full.txt" --format markdown > .nimble/nimble-docs-full.md - Network accessline 209
--url "https://docs.nimbleway.com/llms-full.txt" --format markdown > .nimble/nimble-docs-full.md - Network accessline 209
--url "https://docs.nimbleway.com/llms-full.txt" --format markdown > .nimble/nimble-docs-full.md - Network accessline 213
If bash is also unavailable, use `WebFetch` on `https://docs.nimbleway.com/llms.txt`. - Network accessline 213
If bash is also unavailable, use `WebFetch` on `https://docs.nimbleway.com/llms.txt`.
skills/portfolio-monitoring/SKILL.md
- Broad permissionsline 1
Bash(npm --version) - Broad permissionsline 1
Bash(npm --version) - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 73
If not, ask the user to connect Nimble, in one line on why: "Nimble runs the full research on live sources, with a source for every field. Connecting takes one approval, and new accounts start with a free trial." Then follow https://docs.ni - Network accessline 130
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 130
Offer, one line each, what fits: - **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 131
- **Run it on a list.** One run per record in parallel. See [Running at scale](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/running-at-scale.md). - Network accessline 137
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc - Network accessline 137
Read the page you need, when you need it: [writing the task](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/writing-the-task.md), [sources](https://docs.nimbleway.com/nimble-sdk/web-search-agents/best-practices/sourc
skills/seo-intel/SKILL.md
skills/seo-intel/references/ai-platform-profiles.md
- Network accessline 251
nimble extract --url "https://example.com/llms.txt" --format markdown - Network accessline 251
nimble extract --url "https://example.com/llms.txt" --format markdown - Network accessline 252
nimble extract --url "https://example.com/robots.txt" --format markdown - Network accessline 252
nimble extract --url "https://example.com/robots.txt" --format markdown
skills/seo-intel/references/ai-visibility-agent-prompt.md
- Network accessline 38
2. nimble extract --url "https://www.google.com/search?q={url_encoded_query}" --render --driver vx10-pro --format markdown - Network accessline 38
2. nimble extract --url "https://www.google.com/search?q={url_encoded_query}" --render --driver vx10-pro --format markdown - Network accessline 50
nimble extract --url "https://www.perplexity.ai/search?q={url_encoded_query}" --render --driver vx10-pro --format markdown - Network accessline 50
nimble extract --url "https://www.perplexity.ai/search?q={url_encoded_query}" --render --driver vx10-pro --format markdown - Network accessline 126
"competitor_domain_citations": ["widgetco.com"], "sources": [ {{"url": "https://widgetco.com/features", "title": "WidgetCo Features"}}, - Network accessline 126
"competitor_domain_citations": ["widgetco.com"], "sources": [ {{"url": "https://widgetco.com/features", "title": "WidgetCo Features"}}, - Network accessline 127
"sources": [ {{"url": "https://widgetco.com/features", "title": "WidgetCo Features"}}, {{"url": "https://review-site.com/pm-tools", "title": "Best PM Tools 2026"}} - Network accessline 127
"sources": [ {{"url": "https://widgetco.com/features", "title": "WidgetCo Features"}}, {{"url": "https://review-site.com/pm-tools", "title": "Best PM Tools 2026"}} - Network accessline 128
{{"url": "https://widgetco.com/features", "title": "WidgetCo Features"}}, - Network accessline 128
{{"url": "https://widgetco.com/features", "title": "WidgetCo Features"}}, - Network accessline 129
{{"url": "https://review-site.com/pm-tools", "title": "Best PM Tools 2026"}} - Network accessline 129
{{"url": "https://review-site.com/pm-tools", "title": "Best PM Tools 2026"}}
skills/seo-intel/references/audit-agent-prompt.md
- Network accessline 32
nimble extract-batch --shared-inputs 'format: markdown' --shared-inputs 'render: {render_flag}' --input '{{"url": "https://...page-1"}}' - Network accessline 32
nimble extract-batch --shared-inputs 'format: markdown' --shared-inputs 'render: {render_flag}' --input '{{"url": "https://...page-1"}}' - Network accessline 33
--shared-inputs 'format: markdown' \ --shared-inputs 'render: {render_flag}' \ --input '{{"url": "https://...page-1"}}' \ - Network accessline 33
--shared-inputs 'format: markdown' \ --shared-inputs 'render: {render_flag}' \ --input '{{"url": "https://...page-1"}}' \ - Network accessline 34
--shared-inputs 'render: {render_flag}' \ --input '{{"url": "https://...page-1"}}' \ --input '{{"url": "https://...page-2"}}' \ - Network accessline 34
--shared-inputs 'render: {render_flag}' \ --input '{{"url": "https://...page-1"}}' \ --input '{{"url": "https://...page-2"}}' \ - Network accessline 35
--input '{{"url": "https://...page-1"}}' \ - Network accessline 35
--input '{{"url": "https://...page-1"}}' \ - Network accessline 36
--input '{{"url": "https://...page-2"}}' \ - Network accessline 36
--input '{{"url": "https://...page-2"}}' \ - Network accessline 70
[ {{ "url": "https://...", - Network accessline 70
[ {{ "url": "https://...", - Network accessline 71
{{ "url": "https://...", "status": "success" | "failed" | "parser_empty", - Network accessline 71
{{ "url": "https://...", "status": "success" | "failed" | "parser_empty", - Network accessline 72
"url": "https://...", - Network accessline 72
"url": "https://...",
skills/seo-intel/references/content-gap-agent-prompt.md
- Network accessline 32
nimble extract-batch --shared-inputs 'format: markdown' --input '{{"url": "https://...page-1"}}' - Network accessline 32
nimble extract-batch --shared-inputs 'format: markdown' --input '{{"url": "https://...page-1"}}' - Network accessline 34
--input '{{"url": "https://...page-1"}}' \ - Network accessline 34
--input '{{"url": "https://...page-1"}}' \ - Network accessline 35
--input '{{"url": "https://...page-2"}}' \ - Network accessline 35
--input '{{"url": "https://...page-2"}}' \ - Network accessline 117
"pages": [ { "url": "https://...", - Network accessline 117
"pages": [ { "url": "https://...", - Network accessline 118
{ "url": "https://...", "title": "...", - Network accessline 118
{ "url": "https://...", "title": "...", - Network accessline 119
"url": "https://...", - Network accessline 119
"url": "https://...", - Network accessline 130
}, { "url": "https://...", - Network accessline 130
}, { "url": "https://...", - Network accessline 131
{ "url": "https://...", "error": "extraction failed — 403 Forbidden" - Network accessline 131
{ "url": "https://...", "error": "extraction failed — 403 Forbidden" - Network accessline 132
"url": "https://...", - Network accessline 132
"url": "https://...",
skills/seo-intel/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/seo-intel/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/seo-intel/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
skills/seo-intel/references/seo-audit-checks.md
- Network accessline 262
1. **Build a signature** for each finding: `{page_url}|{rule_number}` (e.g., `https://acme.com/blog|1.1`) - Network accessline 262
1. **Build a signature** for each finding: `{page_url}|{rule_number}` (e.g., `https://acme.com/blog|1.1`) - Network accessline 263
`https://acme.com/blog|1.1`) - Network accessline 263
`https://acme.com/blog|1.1`)
skills/seo-intel/references/seo-extraction-prompt.md
- Network accessline 39
nimble extract-batch --shared-inputs 'format: markdown' --shared-inputs 'render: true' --input '{{"url": "https://...page-1"}}' - Network accessline 39
nimble extract-batch --shared-inputs 'format: markdown' --shared-inputs 'render: true' --input '{{"url": "https://...page-1"}}' - Network accessline 40
--shared-inputs 'format: markdown' \ --shared-inputs 'render: true' \ --input '{{"url": "https://...page-1"}}' \ - Network accessline 40
--shared-inputs 'format: markdown' \ --shared-inputs 'render: true' \ --input '{{"url": "https://...page-1"}}' \ - Network accessline 41
--shared-inputs 'render: true' \ --input '{{"url": "https://...page-1"}}' \ --input '{{"url": "https://...page-2"}}' \ - Network accessline 41
--shared-inputs 'render: true' \ --input '{{"url": "https://...page-1"}}' \ --input '{{"url": "https://...page-2"}}' \ - Network accessline 42
--input '{{"url": "https://...page-1"}}' \ - Network accessline 42
--input '{{"url": "https://...page-1"}}' \ - Network accessline 43
--input '{{"url": "https://...page-2"}}' \ - Network accessline 43
--input '{{"url": "https://...page-2"}}' \ - Network accessline 52
nimble crawl run \ --url "https://{domain}" \ - Network accessline 52
nimble crawl run \ --url "https://{domain}" \ - Network accessline 53
--url "https://{domain}" \ - Network accessline 53
--url "https://{domain}" \ - Network accessline 79
{{ "url": "https://...", - Network accessline 79
{{ "url": "https://...", - Network accessline 80
"url": "https://...", - Network accessline 80
"url": "https://...",
skills/seo-intel/references/serp-query-patterns.md
- Network accessline 81
1. Extract the `url` from each organic result. 2. Normalize the URL: - Strip protocol (`https://`, `http://`). - Network accessline 81
1. Extract the `url` from each organic result. 2. Normalize the URL: - Strip protocol (`https://`, `http://`). - Network accessline 82
2. Normalize the URL: - Strip protocol (`https://`, `http://`). - Strip `www.` prefix. - Network accessline 82
2. Normalize the URL: - Strip protocol (`https://`, `http://`). - Strip `www.` prefix. - Network accessline 83
- Strip protocol (`https://`, `http://`). - Network accessline 83
- Strip protocol (`https://`, `http://`). - Network accessline 92
Example: tracking `example.com` - `https://www.example.com/features` → matches at position 3 - Network accessline 92
Example: tracking `example.com` - `https://www.example.com/features` → matches at position 3 - Network accessline 93
- `https://www.example.com/features` → matches at position 3 - Network accessline 93
- `https://www.example.com/features` → matches at position 3 - Network accessline 94
- `https://blog.example.com/post` → matches at position 7 - Network accessline 94
- `https://blog.example.com/post` → matches at position 7
skills/seo-intel/references/wf-competitor-keywords.md
- Network accessline 81
nimble map --url "https://{domain}" --limit {page_cap * 2} - Network accessline 81
nimble map --url "https://{domain}" --limit {page_cap * 2} - Network accessline 87
nimble map --url "https://{domain}/{section}" --limit {page_cap} - Network accessline 87
nimble map --url "https://{domain}/{section}" --limit {page_cap} - Network accessline 127
|-------|----------|----------------| | < 50 | Sub-agent parallel extract | Spawn `nimble-researcher` agents (max 4), each extracts its assigned URLs with `nimble extract --url {url} --render --format markdown` | | 50-500 | Batch or crawl | - Network accessline 127
|-------|----------|----------------| | < 50 | Sub-agent parallel extract | Spawn `nimble-researcher` agents (max 4), each extracts its assigned URLs with `nimble extract --url {url} --render --format markdown` | | 50-500 | Batch or crawl | - Network accessline 128
| < 50 | Sub-agent parallel extract | Spawn `nimble-researcher` agents (max 4), each extracts its assigned URLs with `nimble extract --url {url} --render --format markdown` | | 50-500 | Batch or crawl | `nimble crawl run --url "https://{dom - Network accessline 128
| < 50 | Sub-agent parallel extract | Spawn `nimble-researcher` agents (max 4), each extracts its assigned URLs with `nimble extract --url {url} --render --format markdown` | | 50-500 | Batch or crawl | `nimble crawl run --url "https://{dom - Network accessline 129
| 50-500 | Batch or crawl | `nimble crawl run --url "https://{domain}" --limit {N} --include-path "{section}" --name "seo-keywords-{domain}-{YYYY-MM-DD}"` per domain; poll with `nimble crawl status --name "..."` | - Network accessline 129
| 50-500 | Batch or crawl | `nimble crawl run --url "https://{domain}" --limit {N} --include-path "{section}" --name "seo-keywords-{domain}-{YYYY-MM-DD}"` per domain; poll with `nimble crawl status --name "..."` | - Network accessline 267
"keywords": ["api", "integration", "webhook"], "page_count": 12, "hub_url": "https://example.com/docs/api-guide" - Network accessline 267
"keywords": ["api", "integration", "webhook"], "page_count": 12, "hub_url": "https://example.com/docs/api-guide" - Network accessline 268
"page_count": 12, "hub_url": "https://example.com/docs/api-guide" } - Network accessline 268
"page_count": 12, "hub_url": "https://example.com/docs/api-guide" } - Network accessline 269
"hub_url": "https://example.com/docs/api-guide" - Network accessline 269
"hub_url": "https://example.com/docs/api-guide" - Network accessline 318
> **Theme shift:** "API integration" grew from 8 to 14 pages (+75%). > New hub page: https://example.com/integrations/api-guide - Network accessline 318
> **Theme shift:** "API integration" grew from 8 to 14 pages (+75%). > New hub page: https://example.com/integrations/api-guide - Network accessline 319
> New hub page: https://example.com/integrations/api-guide - Network accessline 319
> New hub page: https://example.com/integrations/api-guide
skills/seo-intel/references/wf-content-gap.md
- Network accessline 92
nimble map --url "https://{user-domain}" --limit {crawl_depth} - Network accessline 92
nimble map --url "https://{user-domain}" --limit {crawl_depth} - Network accessline 93
nimble map --url "https://{competitor-1}" --limit {crawl_depth} - Network accessline 93
nimble map --url "https://{competitor-1}" --limit {crawl_depth} - Network accessline 94
nimble map --url "https://{competitor-2}" --limit {crawl_depth} - Network accessline 94
nimble map --url "https://{competitor-2}" --limit {crawl_depth}
skills/seo-intel/references/wf-github-seo.md
- Network accessline 44
> "Which GitHub repo should I audit? (URL or owner/name, e.g., > facebook/react or https://github.com/facebook/react)" - Network accessline 44
> "Which GitHub repo should I audit? (URL or owner/name, e.g., > facebook/react or https://github.com/facebook/react)" - Network accessline 45
> facebook/react or https://github.com/facebook/react)" - Network accessline 45
> facebook/react or https://github.com/facebook/react)" - Network accessline 89
nimble extract --url "https://github.com/{owner}/{repo}" --format markdown --render - Network accessline 89
nimble extract --url "https://github.com/{owner}/{repo}" --format markdown --render - Network accessline 119
nimble extract --url "https://github.com/{owner}/{repo}#readme" --format markdown --render - Network accessline 119
nimble extract --url "https://github.com/{owner}/{repo}#readme" --format markdown --render - Network accessline 176
nimble extract --url "https://github.com/{owner}/{repo}/community" --format markdown --render - Network accessline 176
nimble extract --url "https://github.com/{owner}/{repo}/community" --format markdown --render - Network accessline 398
- **`gh` not installed or not authenticated:** Fall back to `nimble extract` for all GitHub data. Metadata comes from the rendered page. README comes from the raw URL (`https://raw.githubusercontent.com/{owner}/{repo}/{branch}/README.md - Network accessline 398
- **`gh` not installed or not authenticated:** Fall back to `nimble extract` for all GitHub data. Metadata comes from the rendered page. README comes from the raw URL (`https://raw.githubusercontent.com/{owner}/{repo}/{branch}/README.md - Network accessline 399
all GitHub data. Metadata comes from the rendered page. README comes from the raw URL (`https://raw.githubusercontent.com/{owner}/{repo}/{branch}/README.md`). Community health is limited to what's visible on the repo page. Note reduced - Network accessline 399
all GitHub data. Metadata comes from the rendered page. README comes from the raw URL (`https://raw.githubusercontent.com/{owner}/{repo}/{branch}/README.md`). Community health is limited to what's visible on the repo page. Note reduced - Network accessline 400
raw URL (`https://raw.githubusercontent.com/{owner}/{repo}/{branch}/README.md`). - Network accessline 400
raw URL (`https://raw.githubusercontent.com/{owner}/{repo}/{branch}/README.md`). - Network accessline 422
- **Base64 decode failure on README:** Fall back to fetching README via `nimble extract --url "https://github.com/{owner}/{repo}#readme" --format markdown`. - Network accessline 422
- **Base64 decode failure on README:** Fall back to fetching README via `nimble extract --url "https://github.com/{owner}/{repo}#readme" --format markdown`. - Network accessline 423
`nimble extract --url "https://github.com/{owner}/{repo}#readme" --format markdown`. - Network accessline 423
`nimble extract --url "https://github.com/{owner}/{repo}#readme" --format markdown`.
skills/seo-intel/references/wf-rank-tracker.md
- Network accessline 145
"keyword": "...", "position": 3, "ranking_url": "https://...", - Network accessline 145
"keyword": "...", "position": 3, "ranking_url": "https://...", - Network accessline 146
"position": 3, "ranking_url": "https://...", "title": "...", - Network accessline 146
"position": 3, "ranking_url": "https://...", "title": "...", - Network accessline 147
"ranking_url": "https://...", - Network accessline 147
"ranking_url": "https://...", - Network accessline 217
"keyword": "project management software", "position": 3, "ranking_url": "https://example.com/features", - Network accessline 217
"keyword": "project management software", "position": 3, "ranking_url": "https://example.com/features", - Network accessline 218
"position": 3, "ranking_url": "https://example.com/features", "title": "Project Management Features | Example", - Network accessline 218
"position": 3, "ranking_url": "https://example.com/features", "title": "Project Management Features | Example", - Network accessline 219
"ranking_url": "https://example.com/features", - Network accessline 219
"ranking_url": "https://example.com/features",
skills/seo-intel/references/wf-site-audit.md
skills/talent-sourcing/SKILL.md
skills/talent-sourcing/references/memory-and-distribution.md
- Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 578
What does NOT count: - A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 579
- A company's homepage (unless the signal is specifically about homepage content) - A generic domain without a path (e.g., `https://widgetco.com`) - "Source: web search" or any non-clickable attribution - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`) - Network accessline 580
- A generic domain without a path (e.g., `https://widgetco.com`)
skills/talent-sourcing/references/nimble-playbook.md
- Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 28
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Access to secretsline 88
[Credential-related source omitted] - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 93
> { > "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 94
> "mcpServers": { > "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } > } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 95
> "nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 232
# Extract article content as markdown (default for content analysis) nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 233
nimble extract --url "https://example.com/article" --format markdown - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 235
# Extract raw HTML (required for <head> metadata: canonical, schema, og, meta tags) nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 236
nimble extract --url "https://example.com" --format html - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 238
# Extract with JavaScript rendering (for dynamic/SPA pages) nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 239
nimble extract --url "https://example.com/spa" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 275
# Async — submit single URL, get task_id, poll for results nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 276
nimble extract-async --url "https://example.com/page" --render --format markdown - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 279
nimble extract-batch \ --shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 280
--shared-inputs 'render: true' --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 281
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 282
--input '{"url": "https://example.com/page-2"}' - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Network accessline 292
nimble map --url "https://example.com/blog" --limit 20 - Access to secretsline 525
[Credential-related source omitted] - Access to secretsline 525
[Credential-related source omitted] - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 723
nimble extract-batch \ --shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 724
--shared-inputs 'format: markdown' \ --input '{"url": "https://example.com/page-1"}' \ --input '{"url": "https://example.com/page-2"}' - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 725
--input '{"url": "https://example.com/page-1"}' \ - Network accessline 726
--input '{"url": "https://example.com/page-2"}' - Network accessline 726
--input '{"url": "https://example.com/page-2"}'
skills/talent-sourcing/references/profile-and-onboarding.md
- Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 162
3. If npm is not available: > "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 163
> "The Nimble CLI requires Node.js/npm. Install Node.js first from > [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" 4. After install, verify: `nimble --version` - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 164
> [nodejs.org](https://nodejs.org), then run: `npm install -g @nimble-way/nimble-cli`" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 176
"nimble": { "type": "http", "url": "https://mcp.nimbleway.com/mcp" - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 177
"type": "http", "url": "https://mcp.nimbleway.com/mcp" } - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 178
"url": "https://mcp.nimbleway.com/mcp" - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 200
> You need a Nimble API key. > 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Network accessline 201
> 1. Go to [app.nimbleway.com](https://app.nimbleway.com) → API Keys - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 203
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted] - Access to secretsline 206
[Credential-related source omitted]
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
Signal confidence: 500 facts
- Broad permissions in the frontmatter of the SKILL.mdaccount-brief/SKILL.md:1High confidence
- Network access in prose of the SKILL.mdaccount-brief/SKILL.md:74Low confidence
- Network access in prose of the SKILL.mdaccount-brief/SKILL.md:131Low confidence
- Network access in prose of the SKILL.mdaccount-brief/SKILL.md:132Low confidence
- Network access in prose of the SKILL.mdaccount-brief/SKILL.md:138Low confidence
- Broad permissions in the frontmatter of the SKILL.mdskills/account-discovery/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdaccount-discovery/SKILL.md:1High confidence
- Network access in prose of the SKILL.mdskills/account-discovery/SKILL.md:73Low confidence
- Network access in prose of the SKILL.mdaccount-discovery/SKILL.md:73Low confidence
- Network access in prose of the SKILL.mdskills/account-discovery/SKILL.md:130Low confidence
- Network access in prose of the SKILL.mdaccount-discovery/SKILL.md:130Low confidence
- Network access in prose of the SKILL.mdskills/account-discovery/SKILL.md:131Low confidence
- Network access in prose of the SKILL.mdaccount-discovery/SKILL.md:131Low confidence
- Network access in prose of the SKILL.mdskills/account-discovery/SKILL.md:137Low confidence
- Network access in prose of the SKILL.mdaccount-discovery/SKILL.md:137Low confidence
- Broad permissions in the frontmatter of the SKILL.mdskills/account-enrichment/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdaccount-enrichment/SKILL.md:1High confidence
- Network access in prose of the SKILL.mdskills/account-enrichment/SKILL.md:74Low confidence
- Network access in prose of the SKILL.mdaccount-enrichment/SKILL.md:74Low confidence
- Network access in prose of the SKILL.mdskills/account-enrichment/SKILL.md:132Low confidence
- Network access in prose of the SKILL.mdaccount-enrichment/SKILL.md:132Low confidence
- Network access in prose of the SKILL.mdskills/account-enrichment/SKILL.md:133Low confidence
- Network access in prose of the SKILL.mdaccount-enrichment/SKILL.md:133Low confidence
- Network access in prose of the SKILL.mdskills/account-enrichment/SKILL.md:139Low confidence
- Network access in prose of the SKILL.mdaccount-enrichment/SKILL.md:139Low confidence
- Broad permissions in the frontmatter of the SKILL.mdskills/account-signals/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdaccount-signals/SKILL.md:1High confidence
- Network access in prose of the SKILL.mdskills/account-signals/SKILL.md:73Low confidence
- Network access in prose of the SKILL.mdaccount-signals/SKILL.md:73Low confidence
- Network access in prose of the SKILL.mdskills/account-signals/SKILL.md:131Low confidence
- Network access in prose of the SKILL.mdaccount-signals/SKILL.md:131Low confidence
- Network access in prose of the SKILL.mdskills/account-signals/SKILL.md:132Low confidence
- Network access in prose of the SKILL.mdaccount-signals/SKILL.md:132Low confidence
- Network access in prose of the SKILL.mdskills/account-signals/SKILL.md:138Low confidence
- Network access in prose of the SKILL.mdaccount-signals/SKILL.md:138Low confidence
- Broad permissions in the frontmatter of the SKILL.mdskills/brand-mention-monitor/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdbrand-mention-monitor/SKILL.md:1High confidence
- Network access in prose of the SKILL.mdskills/brand-mention-monitor/SKILL.md:344Low confidence
- Network access in prose of the SKILL.mdbrand-mention-monitor/SKILL.md:344Low confidence
- Network access in prose of the SKILL.mdskills/brand-mention-monitor/SKILL.md:345Low confidence
- Network access in prose of the SKILL.mdbrand-mention-monitor/SKILL.md:345Low confidence
- Network access in prose of the SKILL.mdskills/brand-mention-monitor/SKILL.md:346Low confidence
- Network access in prose of the SKILL.mdbrand-mention-monitor/SKILL.md:346Low confidence
- Network access in prose of the SKILL.mdskills/brand-mention-monitor/SKILL.md:347Low confidence
- Network access in prose of the SKILL.mdbrand-mention-monitor/SKILL.md:347Low confidence
- Network access in prose of the SKILL.mdskills/brand-mention-monitor/SKILL.md:348Low confidence
- Network access in prose of the SKILL.mdbrand-mention-monitor/SKILL.md:348Low confidence
- Network access in prose of the SKILL.mdskills/brand-mention-monitor/SKILL.md:388Low confidence
- Network access in prose of the SKILL.mdbrand-mention-monitor/SKILL.md:388Low confidence
- Network access in prose of the SKILL.mdskills/brand-mention-monitor/SKILL.md:389Low confidence
and 450 more
Only the first 500 facts are listed.
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md skills/account-brief/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/account-brief/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/account-brief/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/account-brief/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/account-brief/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.