sergekostenchuk/ui-ux-agent-skill-system

llm-citation-monitor

Plan and record evidence-backed LLM and AI-search citation checks across approved assistant/search surfaces with timestamped queries, locales, modes, cited URLs, snippets, screenshots or transcripts, and caveats.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill llm-citation-monitor

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

LLM Citation Monitor

Use this skill after the target site's SEO/LLM discovery layer exists and the user wants to measure assistant/search citation visibility.

Read references/citation-evidence-policy.md before producing a monitoring plan or report.

Owns

  • target question matrix;
  • manual observation workflow;
  • citation report template;
  • assistant/search surface evidence policy;
  • competitor citation capture;
  • caveats for personalization, locale, freshness, and account state;
  • refusal of unsupported citation claims.

Does Not Own

  • assistant account credentials;
  • bypassing bot protections;
  • scraping assistant/search surfaces without approval;
  • changing robots, WAF, auth, or crawler policy;
  • ranking claims;
  • content/schema implementation.

Workflow

  1. Define target site, page set, audience, locale, and target questions.
  2. Classify query intent: brand, topic, problem, comparison, how-to, or citation-check.
  3. Choose approved observation mode: manual, exported transcript, screenshot, API/tool report, or public fetch.
  4. For each run, record surface, model/search product if visible, date/time, locale, account state, query text, answer summary, cited URLs, quote/snippet, and caveats.
  5. Capture competitor citations separately from target citations.
  6. Mark missing citations as not observed, not as "does not cite anywhere".
  7. Produce a report using assets/citation-report.template.md.
  8. Hand off site-content or technical fixes to SEO/LLM architecture skills.

Non-Negotiables

  • Do not claim "ChatGPT cites us" without direct citation evidence.
  • Do not treat one personalized answer as universal ranking.
  • Do not store assistant credentials, cookies, account tokens, or private conversation data in skill files.
  • Do not bypass paywalls, auth, robots, WAF, or tool restrictions.
  • Do not scrape surfaces against terms of service.
  • Do not publish screenshots/transcripts containing private user data.

Safety And Privacy Boundaries

  • Reports should contain only approved public query text, public cited URLs, and redacted/private-safe snippets.
  • If a screenshot or transcript includes account details, remove them before adding to shared artifacts.
  • If a user provides a private assistant transcript, summarize it locally and ask before storing it.
  • Treat model version, locale, date/time, and account state as part of the evidence, not incidental metadata.

Evidence Labels

  • Cited: target URL appears as a cited/source URL in the answer or citation panel.
  • Mentioned: target brand/page mentioned but not cited.
  • Not observed: no target citation in this run.
  • Competitor cited: another domain was cited for the target question.
  • Invalid evidence: missing timestamp, surface, query, or cited URL.

Validation

Validate skill edits with:

bash
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $HOME/SKILL/skills/llm-citation-monitor
python3 $HOME/SKILL/plans/seo-llm-skill-cluster/scripts/lint_skill_cluster.py $HOME/SKILL

Forward tests live in evals.json.

Output Shape

Return:

  1. Monitoring objective and target pages.
  2. Query matrix.
  3. Approved surfaces and observation mode.
  4. Citation evidence table.
  5. Competitor citation table.
  6. Caveats and limitations.
  7. Fix backlog routed to the correct skill owner.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
sergekostenchuk
コミュニティ

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

導入数
1
GitHub Stars
32
更新日
9月13日
sergekostenchuk
コミュニティ

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

導入数
1
GitHub Stars
32
更新日
9月13日
sergekostenchuk
コミュニティ

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

導入数
1
GitHub Stars
32
更新日
9月13日
sergekostenchuk
コミュニティ

figma-canvas-editor

Create and edit native Figma canvas objects with MCP when explicitly scoped. Use this skill when the user asks to add or change frames, sections, components, instances, auto layout, variables, styles, FigJam objects, connectors, Slides objects, or selected nodes in Figma, and when the task requires mutation evidence, rollback-aware scope, and design-system consistency.

導入数
1
GitHub Stars
32
更新日
9月13日