SkillsAdd

dineway/dineway-skills

dineway-seo-providers

Use Dineway Tools through CLI or built-in MCP for Firecrawl and DataForSEO research.

First seen Jun 16, 2026

Installation

$ npx skills add dineway/dineway-skills --skill dineway-seo-providers
View on skills.sh ↗ GitHub repository ↗

Summary

  • Use Dineway Tools through CLI or built-in MCP for Firecrawl and DataForSEO research.
  • Use for provider selection, Firecrawl scrape/map/crawl/search, DataForSEO SERP/maps/keywords/competitors/AI visibility, raw provider response interpretation, credit- or BYOK-aware research, and evidence-backed SEO recommendations.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

cli-providers Similar name
diegosouzapw/omniroute

Manage provider connections from the CLI: list available/configured providers, add, test, test-…

1 installs
omni-providers Similar name
diegosouzapw/omniroute

Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List…

16 installs
syncing-test-providers Similar name
forcedotcom/sf-skills

Re-syncs a configured DevOps Center test provider on a pipeline to pick up new test suites, via…

267 installs

Also in this package

Other skills from dineway/dineway-skills · top by installs.

npx skills add dineway/dineway-skills
building-restaurant-site 33 dineway-cli 27 planning-with-files 25 enrich-place-details 22 brainstorming 22 frontend-design 22 dineway-seo-images 11 dineway-seo-schema 11 dineway-seo-competitor-pages 11 dineway-seo-cluster 11

Browse all from dineway/dineway-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,955 B
  • docs SUMMARY.md 344 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 11 installs

SKILL.md

Dineway SEO Providers

Use this child skill for Firecrawl and DataForSEO research through Dineway Tools. It may be invoked directly, but it must preserve the shared Dineway SEO boundaries.

Required References

  • Load ../dineway-seo/references/provider-selection.md.
  • Load ../dineway-seo/references/security-boundaries.md before every provider call.
  • Load ../dineway-seo/references/firecrawl.md for Firecrawl scrape/map/crawl/search.
  • Load ../dineway-seo/references/dataforseo.md for DataForSEO SERP/maps/keywords/competitors/AI visibility.
  • Load ../dineway-seo/references/apply-loop.md before turning provider evidence into Dineway changes.

Workflow

  1. Decide whether provider data is necessary; use current Dineway state and user-supplied facts when enough.
  2. Choose DataForSEO for SERP, maps, keywords, competitor-domain, and AI visibility data.
  3. Choose Firecrawl for scrape, map, bounded crawl jobs, and search plus markdown extraction.
  4. Keep every request bounded by URL/query, location/language, and limit.
  5. Use only Dineway Tools. Run dineway tools discover, inspect the selected contract, and then use

dineway tools run for human, script, or CI control. Use the generic toolsdiscover, toolsinspect, and tools_run MCP operations only when CLI is unavailable.

  1. Interpret raw provider payloads as evidence, then route recommendations to content brief, cluster, competitor, schema, image, or apply-loop workflows.

Boundaries

  • Never ask for or store Firecrawl/DataForSEO secret values. CLI BYOK may reference environment

variable names; built-in MCP may use encrypted site BYOK.

  • Do not use third-party provider MCP servers. Dineway's built-in generic Tools MCP surface is

allowed. First-party/local crawling and Browser Use belong to the calling Skill; this Skill handles Forgeway Integration evidence only.

  • Do not expose provider credentials, billing secrets, or internal cache details.
  • Treat provider cost/status/task metadata as operational evidence, not visitor-facing copy.
  • Do not perform unbounded crawling or broad audits without explicit limits.
  • Hosted provider use requires verified Forgeway account access. MCP requires an Author-or-higher

actor with tools:read and tools:run, or admin; anonymous/shadow users are out of scope.

Output

Use the root dineway-seo output contract. Include Provider Chosen, Reason, Command/API Family, Inputs and Limits, Relevant Raw Response Fields, Dineway Implications, Provider Calls Used, Skipped or Risky Claims, and Verification Plan.