소스 정보
- 저장소
- tomevault-io/skills-registry
- 최근 소스 활동
- 2026년 7월 3일 19:45
- 감지된 SKILL.md 언어
- 영어
- 스타
- 0
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/tomevault-io/skills-registry --skill marketing-seo-research명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
| name | marketing-seo-research |
| description | >- Use when this capability is needed. |
Keyword research + search metrics to enrich content ideas and drafts with a
target_keyword and an SEO context block.
content/ideas/{slug}.md)workspace/firm/profile.md — industry and geography/location (DataForSEO
location name format, e.g. "Poland", "United States"). Default location: Poland.
researchKeywords(topic, industry, location):
getKeywordData(keyword, location) →
{ keyword, search_volume, cpc, competition, competition_level }
(default location Poland). Stored as the primary_keyword, source: dataforseo.source: ai.AI keyword query (verbatim shape):
Suggest 5 high-value SEO keywords for B2B content about "{topic}"
[in the {industry} industry]. Format: one keyword per line, no numbering,
just the keyword phrases.
Dry-run (no keys): propose keywords from topic + industry knowledge, mark
source: dry-run.
Choose the most relevant, realistic keyword (intent + achievable competition). Prefer specific long-tail over generic head terms for PSF/B2B.
generateSeoContext(topic, targetKeyword) → a short block for content prompts.
It starts with a SEO Context: header, the target keyword, and (only when
DataForSEO is available) one metrics line with monthly search volume and
competition level — CPC is not included here:
SEO Context:
Target keyword: {target_keyword}
Keyword metrics: {search_volume} monthly searches, competition: {competition_level}
When the keyword research feeds idea generation, the prompt also nudges the model to "include target keywords naturally in content titles where appropriate" — it does not prescribe specific placements (title / first paragraph / H2).
target_keyword: in the relevant content/ideas/{slug}.md frontmatter.workspace/marketing/seo/{topic-slug}.md:---
topic:
location:
source: dataforseo | ai | dry-run
primary_keyword:
search_volume:
competition:
suggestions: []
date: 2026-06-01
---
marketing-content-ideas can call this to attach target_keyword per idea.marketing-content-blog-post should weave the SEO context block into blog
drafts.marketing-service-page should use SEO context for standalone service pages.
LinkedIn/X do not use SEO research.target_keyword per content piece; keep secondary as suggestions.DATAFORSEO_LOGIN=
DATAFORSEO_PASSWORD=
EXA_API_KEY= # or Perplexity — AI keyword fallback
| Skill | When |
|---|---|
marketing-content-ideas | Attach target keywords to ideas |
marketing-content-blog-post | Consume SEO context in blog drafts |
marketing-service-page | Consume SEO context in standalone service pages |
firm-context | Industry + target location |
Source: b2bforce/b2bforce — distributed by TomeVault.