linkable-asset-planning
Plan, audit, and prioritize linkable assets that publishers, curators, experts, and community owners have a real reason to cite. Use when creating link-worthy content ideas, auditing existing assets, turning market pains into assets, analyzing competitor linkable content, or deciding what to build before link prospecting and outreach.
- License 许可
- MIT
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- linkable-asset-planning
- license
- MIT
- metadata
- { "tags": "seo,link-building,content-strategy,assets,organic-growth", "version": "0.1.0", "category": "Marketing", "displayName": "Linkable Asset Planning" }
- description
- Plan, audit, and prioritize linkable assets that publishers, curators, experts, and community owners have a real reason to cite. Use when creating link-worthy content ideas, auditing existing assets, turning market pains into assets, analyzing competitor linkable content, or deciding what to build before link prospecting and outreach.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 4
- 参考文档references/core/examples.md1.9 KB
- 参考文档references/core/knowledge.md1.9 KB
- 参考文档references/core/rules.md1.9 KB
- 参考文档workflows/plan-linkable-asset.md2.8 KB
03 SKILL.md 正文
Linkable Asset Planning
Use this skill to identify, evaluate, and plan assets that deserve links before a campaign starts. It helps agents turn organizational strengths, market pains, and proven link patterns into cite-worthy resources.
This skill is derived from Garrett French and Eric Ward's Ultimate Guide to Link Building and uses transformed guidance with durable book-topic references. Do not copy book prose into user outputs.
Quick Start
- Use the Contents table below to choose the smallest useful reference set.
- Use
workflows/plan-linkable-asset.mdfor a full asset plan. - Start with the linker audience and the problem their readers need solved.
- Audit existing assets before recommending new production.
- Return prioritized asset concepts with evidence, value add, required resources, promotion angle, and conversion path.
Default Output
When the user asks for linkable asset ideas or an asset audit, return:
- Objective - business goal, SEO goal, and target audience.
- Linker audience map - who might link and why.
- Existing asset inventory - current assets, link evidence, gaps, and improvements.
- Market evidence - competitor and publisher assets that already earn links.
- Pain map - recurring problems, tasks, and content gaps.
- Recommended asset concepts - format, value add, required resources, prospects, and risk.
- Priority table - link potential, effort, differentiation, confidence, and next action.
Contents
| Need | Start Here |
|---|---|
| Understand linkable assets | references/core/knowledge.md |
| Apply asset planning rules | references/core/rules.md |
| See asset examples | references/core/examples.md |
| Plan or audit assets | workflows/plan-linkable-asset.md |
Core Posture
- Useful assets earn links because they help a defined audience.
- Linker audiences may differ from buyer personas.
- The market reveals what is linkable through pages that already attract links.
- Asset planning should happen before prospecting and outreach.
- Conversion paths are allowed, but usefulness must stand on its own.
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.