Skills geo-content-brief-skill

📦

geo-content-brief-skill

Name: geo-content-brief-skill
Author: yaojingang

Content revision r1 Low Risk 🌐 Network access📁 Filesystem access⚙️ External commands

Create Chinese GEO Content Briefs

Teams often receive scattered interviews, keywords, competitor notes, and channel limits that are hard to turn into writer-ready direction. This skill organizes those inputs into a focused Chinese GEO content brief with structure, evidence needs, risks, and next actions.

Supports: Claude Codex Code(CC)

📊 74 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "geo-content-brief-skill" from https://skillstore.io/skills/yaojingang-geo-content-brief-skill.md and its manifest at https://skillstore.io/api/skills/yaojingang-geo-content-brief-skill/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/yaojingang-geo-content-brief-skill.md Signed manifest GET /api/skills/yaojingang-geo-content-brief-skill/manifest Signed lockfile GET /api/skills/yaojingang-geo-content-brief-skill/lockfile

Test it

Using "geo-content-brief-skill". Customer interview notes, eight GEO keywords, a Zhihu channel limit, and a list of banned brand phrases.

Expected outcome:

A one-page Chinese brief with input summary, target reader, search intent, recommended angle, section outline, evidence checklist, risk zone, and writer next steps.

Using "geo-content-brief-skill". Only a keyword list and a rough product direction are available.

Expected outcome:

A gap list, up to three clarification questions, and a marked draft brief that labels unverified assumptions as pending evidence.

Using "geo-content-brief-skill". Competitor page summaries plus internal product notes for a comparison article.

Expected outcome:

A brief that separates competitor signals from owned claims, proposes a differentiated angle, and lists proof needed before drafting.

Security Audit

Low Risk

v4 • 7/8/2026 Open versioned report

Static analysis produced many high-severity hits, but adjudication found they are false positives from Chinese text, Markdown backticks, generated reports, relative documentation links, and static HTML/SVG. No prompt injection, automatic network request, credential access, screenshot upload flow, command execution path, or encoded executable payload was found in the reviewed skill files. One low-severity semantic issue remains: a generated report exposes a local developer path.

Files scanned

14,096

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Low

reports/review-studio.html:560

Local Developer Path Disclosure

A generated review page includes an absolute local macOS path in a migration guide link. This leaks the author username and local project layout, although it does not execute code.

The cited line contains an absolute /Users/laoyao/... href in generated HTML. The impact is limited to metadata disclosure because the link is static content.

Risk Factors

🌐 Network access (13)

reports/compiled_targets.json:72 reports/compiled_targets.json:521 reports/compiled_targets.json:970 reports/compiled_targets.json:1403 reports/compiled_targets.json:1836 reports/review-studio.json:2073 reports/review-studio.json:2522 reports/review-studio.json:2971 reports/review-studio.json:3404 reports/review-studio.json:3837 reports/skill-ir.json:35 reports/system-model.json:77 reports/system-model.md:72

📁 Filesystem access (8)

reports/review-studio.html:560 reports/review-studio.html:570 reports/review-studio.json:88 reports/review-studio.json:211 reports/review-studio.json:300 reports/review-studio.json:400 reports/review-studio.json:446 reports/review-studio.json:564

⚙️ External commands (25)

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/yaojingang-geo-content-brief-skill/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/yaojingang-geo-content-brief-skill/security.svg)](https://skillstore.io/skills/yaojingang-geo-content-brief-skill?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/yaojingang-geo-content-brief-skill?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/yaojingang-geo-content-brief-skill/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/yaojingang-geo-content-brief-skill.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

yaojingang. (2026). geo-content-brief-skill security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/yaojingang-geo-content-brief-skill/audits/4

BibTeX citation

@techreport{yaojingang-yaojingang-geo-content-brief-skill-2026,
  author = {yaojingang},
  title = {geo-content-brief-skill security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/yaojingang-geo-content-brief-skill/audits/4},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "geo-content-brief-skill security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "yaojingang"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/yaojingang-geo-content-brief-skill/audits/4"
identifiers:
  - type: other
    value: "skillstore:yaojingang-geo-content-brief-skill:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prepare Writer Handoffs

Turn raw research, customer notes, and channel rules into a brief that writers can execute without guessing.

Plan GEO Topic Angles

Map keywords, intent, competitor signals, and evidence gaps into article angles and structure options.

Review Brief Quality

Check whether a planned brief includes audience, evidence, risk language, and next steps before drafting starts.

Try These Prompts

Basic Brief From Notes

Use geo-content-brief-skill. Turn these interview notes, keywords, channel constraints, and brand boundaries into a Chinese GEO content brief for a writer.

Clarify Missing Inputs

Use geo-content-brief-skill. Review my partial keyword list and draft direction. Ask up to three clarification questions before creating the brief.

Competitor-Informed Brief

Use geo-content-brief-skill. Compare these competitor page summaries with our product notes and create a brief with angle, structure, evidence needs, and risk warnings.

Editorial Gate Review

Use geo-content-brief-skill. Audit this planned Chinese GEO brief against the review checklist. Identify missing evidence, weak structure, risky claims, and next actions.

Best Practices

Provide interview notes, keywords, channel rules, audience details, and brand restrictions together when possible.
Mark which claims are verified and which facts still need evidence before drafting starts.
Use the review checklist before sending the brief to a writer or editor.

Avoid

Do not ask it to write a complete long-form article when you need a planning brief.
Do not treat unsupported search volume, rankings, screenshots, or quotes as facts.
Do not use the generated report command examples as trusted runtime commands without review.