New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Logseq Server Usage Stats

by logseq in logseq/logseq

Collect, interpret, and troubleshoot db-sync server usage stats (total users/graphs, active users/graphs in N days, created-today metrics) using the deps/db-sync scripts and D1 schema.

AGPL-3.0Auto-check passedKnowledge Management

Install Logseq Server Usage Stats

skills CLI
$ npx skills add logseq/logseq --skill logseq-server-usage-stats -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install logseq/logseq logseq-server-usage-stats --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/logseq/logseq.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/logseq-server-usage-stats .claude/skills/logseq-server-usage-stats && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
logseq-server-usage-stats
GitHub stars
45k
Token cost
~550 tokens
SKILL.md length
203 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Collect, interpret, and troubleshoot db-sync server usage stats (total users/graphs, active users/graphs in N days, created-today metrics) using the deps/db-sync scripts and D1 schema.

  • Works in 5 steps: Separate one-off stats query cost from… → Treat request-path activity touch as the… → Verify whether touch happens only on… → …
  • Requests involve show-usage-stats
  • SKILL.md covers Run stats, Metric semantics, Cost review workflow and Troubleshooting
  • Calls pnpm

What it does

Logseq Server Usage Stats is an agent skill from logseq/logseq. Collect, interpret, and troubleshoot db-sync server usage stats (total users/graphs, active users/graphs in N days, created-today metrics) using the deps/db-sync scripts and D1 schema. Use when requests involve show-usage-stats, server usage reporting, active-entity counting, or Cloudflare D1 cost impact of usage tracking.

Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management. It works with Cloudflare. The repository describes itself as: A privacy-first, open-source platform for knowledge management and collaboration. Download link: http://github.com/logseq/logseq/releases. roadmap: https://logseq.io/p/NX4mcggEV. The licence is AGPL-3.0.

When your agent uses it

  • Requests involve show-usage-stats
  • Server usage reporting
  • Active-entity counting
  • Cloudflare D1 cost impact of usage tracking

Example prompts

  • “/logseq-server-usage-stats”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Separate one-off stats query cost from continuous request-path tracking cost.
  2. Treat request-path activity touch as the primary D1 cost driver.
  3. Verify whether touch happens only on successful responses in the current code.
  4. Estimate cost with traffic shape
  5. Recommend reducing write attempts before adding new infrastructure

What it can do on your machine

Read from SKILL.md and the folder at commit 22a29b3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Logseq Server Usage Stats loads about 550 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 203 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
When it runs · the whole SKILL.md, loaded when a task matches
~550

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from logseq/logseq at commit 22a29b3, republished under its AGPL-3.0 licence (© logseq). 203 words, ~550 tokens.

Download SKILL.mdSave it as .claude/skills/logseq-server-usage-stats/SKILL.md (or your agent's skills folder).
name
logseq-server-usage-stats
description
Collect, interpret, and troubleshoot db-sync server usage stats (total users/graphs, active users/graphs in N days, created-today metrics) using the `deps/db-sync` scripts and D1 schema. Use when requests involve `show-usage-stats`, server usage reporting, active-entity counting, or Cloudflare D1 cost impact of usage tracking.

Logseq Server Usage Stats

Use this skill to run and explain server usage stats for db-sync.

Run stats

Use the packaged command from deps/db-sync:

bash
cd deps/db-sync
pnpm show-usage-stats
pnpm show-usage-stats --days 7
pnpm show-usage-stats --json
pnpm show-usage-stats --env staging --days 30 --json
pnpm show-usage-stats --env local --json

Metric semantics

Interpret output with these rules:

  • active_users_last_n_days and active_graphs_last_n_days come from deduplicated rows in daily_active_entities.
  • active_since_utc and today_utc are UTC-day boundaries.
  • users_created_today reads users.created_at in today UTC range.
  • graphs_created_today reads graphs.created_at in today UTC range.

When discussing data quality, explicitly mention:

  • activity is counted from request-path touch logic, not client app foreground time
  • active metrics are per day per entity, not per request

Cost review workflow

When asked about Cloudflare cost impact:

  1. Separate one-off stats query cost from continuous request-path tracking cost.
  2. Treat request-path activity touch as the primary D1 cost driver.
  3. Verify whether touch happens only on successful responses in the current code.
  4. Estimate cost with traffic shape:
    • successful sync request volume
    • unique (day, entity_type, entity_id) volume
    • cache effectiveness under multi-isolate execution
  5. Recommend reducing write attempts before adding new infrastructure:
    • keep touch only on meaningful successful routes
    • avoid duplicate touch points on read-heavy endpoints

Troubleshooting

If command fails, check in order:

  1. Wrong environment or wrangler config path.
  2. Missing migrations/tables/columns.
  3. D1 auth/project context mismatch.
  4. Non-integer --days value (>= 1 required).

© logseq, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/logseq-server-usage-stats of logseq/logseq.

Open the folder on GitHubat commit 22a29b3

Compare with similar skills

Logseq Server Usage Stats next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Logseq Server Usage Stats compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Logseq Server Usage Stats this skilllogseq/logseq45k—~550Automated safety check: PassAGPL-3.0
Gitnexus ExplorerTommy-yw/RunbookHermes5463 repos~1.8kAutomated safety check: PassMIT
Cf Crawldavila7/claude-code-templates32k—~2.6kAutomated safety check: NotesMIT
Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill2.5k2 repos~3.2kAutomated safety check: PassNone
Obsidian CLIAtmosphere/atmosphere3.8k13 repos~795Automated safety check: PassApache-2.0
Karpathy LLM WikiAstro-Han/karpathy-llm-wiki2.4k—~3.6kAutomated safety check: PassMIT

Similar skills

  • Gitnexus Explorer

    Tommy-yw/RunbookHermes

    Index a codebase with GitNexus and serve an interactive knowledge graph via web UI + Cloudflare tunnel.

    546 GitHub starsUsed in 3 repos~1.8k tokens
    Knowledge ManagementAuto-check passed

  • Cf Crawl

    davila7/claude-code-templates

    Crawl entire websites using Cloudflare Browser Rendering /crawl API.

    32k GitHub stars~2.6k tokensUpdated today
    Knowledge ManagementAuto-check: notes

  • Baoyu URL To Markdown

    sdyckjq-lab/llm-wiki-skill

    Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.

    2.5k GitHub starsUsed in 2 repos~3.2k tokens
    Knowledge ManagementAuto-check passed

  • Obsidian CLI

    Atmosphere/atmosphere

    Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.

    3.8k GitHub starsUsed in 13 repos~795 tokens
    Knowledge ManagementAuto-check passed

  • Karpathy LLM Wiki

    Astro-Han/karpathy-llm-wiki

    A skill your agent uses when building or maintaining a personal LLM-powered knowledge base.

    2.4k GitHub stars~3.6k tokensUpdated 2 mo ago
    Knowledge ManagementAuto-check passed

  • Zlibrary To Notebooklm

    zstmfhy/zlibrary-to-notebooklm

    自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式，自动转换，一键创建知识库。

    1.7k GitHub starsUsed in 1 repo~968 tokens
    Knowledge ManagementAuto-check passed

More from logseq/logseq

All 12 skills in this repo

  • Logseq Review Workflow Eval

    logseq/logseq

    Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…

    45k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Esm Cjs Risk Scan

    logseq/logseq

    Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.

    45k GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • Logseq Plugin SDK

    logseq/logseq

    Build, debug, or review Logseq plugins with the @logseq/libs SDK (TypeScript/JavaScript, iframe/shadow sandboxed).

    45k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Logseq CLI

    logseq/logseq

    Operate the current Logseq command-line interface to inspect or modify graphs, pages, blocks, tasks, tags, and properties; run Datascript queries; show page/block trees; manage graphs; and manage…

    45k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Logseq Dependency Upgrade

    logseq/logseq

    Audit, plan, and refresh dependency upgrades for the Logseq repository by scanning every non-gitignored package.json, deps.edn, bb.edn and nbb.edn manifest, checking latest upstream versions…

    45k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Logseq I18n

    logseq/logseq

    Logseq i18n workflow for adding, renaming, reviewing, or editing translation keys and user-facing strings.

    45k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Logseq Server Usage Stats

What does Logseq Server Usage Stats do?

Collect, interpret, and troubleshoot db-sync server usage stats (total users/graphs, active users/graphs in N days, created-today metrics) using the deps/db-sync scripts and D1 schema. Logseq Server Usage Stats is an agent skill from logseq/logseq. Collect, interpret, and troubleshoot db-sync server usage stats (total users/graphs, active users/graphs in N days, created-today metrics) using the deps/db-sync scripts and D1 schema.

When should I use Logseq Server Usage Stats?

Logseq Server Usage Stats fits situations like: requests involve show-usage-stats; server usage reporting; active-entity counting; cloudflare D1 cost impact of usage tracking.

How do I install Logseq Server Usage Stats in Claude Code?

Run `npx skills add logseq/logseq --skill logseq-server-usage-stats -a claude-code`. Or copy the skill folder (.agents/skills/logseq-server-usage-stats in logseq/logseq) into .claude/skills/logseq-server-usage-stats in your project. Claude Code loads it when a task matches its description.

How do I install Logseq Server Usage Stats in Codex?

Run `npx skills add logseq/logseq --skill logseq-server-usage-stats -a codex`. Or copy the skill folder (.agents/skills/logseq-server-usage-stats in logseq/logseq) into .agents/skills/logseq-server-usage-stats in your project. Codex loads it when a task matches its description.

Can I use Logseq Server Usage Stats in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add logseq/logseq --skill logseq-server-usage-stats -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/logseq-server-usage-stats, .gemini/skills/logseq-server-usage-stats, .github/skills/logseq-server-usage-stats and .opencode/skills/logseq-server-usage-stats in your project.

What does Logseq Server Usage Stats need to run?

Going by SKILL.md and its folder, Logseq Server Usage Stats needs the command-line tools its instructions call (pnpm).

Does Logseq Server Usage Stats access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Logseq Server Usage Stats safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Logseq Server Usage Stats use?

Logseq Server Usage Stats is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Logseq Server Usage Stats use?

About 550 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Logseq Server Usage Stats?

Skills that share tags, products or a category with Logseq Server Usage Stats: Gitnexus Explorer (Tommy-yw/RunbookHermes, 546 stars), Cf Crawl (davila7/claude-code-templates, 32k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars) and Obsidian CLI (Atmosphere/atmosphere, 3.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Logseq Server Usage Stats?

logseq (a GitHub organization) maintains it in logseq/logseq, which has 45,158 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

Source: logseq/logseq on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.