logseq-asset-linker

スター8

フォーク1

更新日2026年7月27日 14:03

Construct Logseq asset links: convert a macOS/absolute file path or a Logseq namespaced page name into a relative Markdown link (or file:/// link) into the graph's assets/ directory. Use when the user gives a file path or [[Namespace/Page]] and wants the asset/image/PDF link, an asset filename, or an asset folder path. Do not use for ordinary page wikilinks (logseq-core / logseq-link-hygiene).

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

codekiln

codekiln/logseq-encode-garden

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Logseq asset linker

Produce copy-pasteable asset links relative to a page in pages/.

Quick rules

Relative links into assets/ are formed from a typical page location (logseq/pages/somepage.md), so they start ../assets/....
Image link: ![name](../assets/path). File link: [name](../assets/path). Folder link: [name](../assets/folder).
Use file:/absolute/path only when the user explicitly wants a direct file link.
For namespaced assets, convert / → __ (double underscore) in the filename, and sanitize non-alphanumeric chars to _.
Always return the result as a code snippet for easy copying.

Read references/asset-link-construction.md for the full use cases, examples, and the file:/// handling rules.

このリポジトリの他の Skills

同じリポジトリ

ask-my-agent-anything-about-me

codekiln/logseq-encode-garden

Ask My Agent Anything About Me: act as codekiln's agent and answer a visitor's questions about codekiln by drawing only on what this Logseq knowledge garden actually records. Never speak in codekiln's first person. Use when someone has cloned this repo to get to know codekiln and asks things like "who is codekiln?", "what do they work on / believe / value?", "what are their preferences, principles, or projects?", "what are they reading or thinking about lately?". Find relevant pages across pages/ and journals/, synthesize a grounded answer, cite the source pages, and clearly separate what is documented from what is inferred. Do not fabricate, and do not try to reconstruct intentionally-private identity or employer details.

2026-07-278

diataxis-docs

codekiln/logseq-encode-garden

Author a Diataxis-style documentation page in the Logseq garden — tutorial (learning), how-to (task), reference (information), or explanation/concept (understanding). Use when the user asks to create or restructure a How To, Tutorial, Reference, or Concept/Explanation page, or asks which Diataxis type fits. Adds the right `[[Diataxis/...]]` tag and namespace. Do not use for non-doc pages or to edit existing protected `tags::`.

2026-07-278

git-conventions

codekiln/logseq-encode-garden

Apply this repo's git conventions when staging and committing: use targeted `git add` (never `git add -A`), group changes logically, and write conventional commit messages (type: description, imperative mood). Use when the user asks to commit, stage, or write a commit message in this repo. Do not use for branch/PR review workflows.

2026-07-278

landing-the-plane

codekiln/logseq-encode-garden

Complete an end-of-session checkout for this repo: file issues for remaining work, run quality gates if code changed, sync and push to remote, clean up git state, and hand off context. Use when the user says "land the plane", "wrap up", "finish the session", or asks to make sure everything is committed and pushed. Work is not done until `git push` succeeds.

2026-07-278

logseq-ai-model

codekiln/logseq-encode-garden

Reference or document AI models in the garden using provider namespaces and singular naming. Use when mentioning a model in passing/changelogs, creating a model stub, or authoring a detailed model page with features, benchmarks, tiers, access, and specs. Covers OpenAI/Anthropic/Google/DeepSeek/xAI model link formats and model-code aliases. Do not use for general entity creation (logseq-entity) or non-model pages.

2026-07-278

logseq-block-ids

codekiln/logseq-encode-garden

Work safely with Logseq block IDs (`id::` properties) and `((uuid))` block references when moving, copying, or removing blocks across graph pages. Use when relocating a block that has an id::, creating a new ((ref)) to a block, deciding whether an id:: can be removed, or diagnosing refs that won't render. Baseline safety (never backtick a live ref/link; keep id:: with its block) is in logseq-core; this skill has the full move/copy/reindex procedures.

2026-07-278

name	logseq-asset-linker
description	Construct Logseq asset links: convert a macOS/absolute file path or a Logseq namespaced page name into a relative Markdown link (or file:/// link) into the graph's assets/ directory. Use when the user gives a file path or [[Namespace/Page]] and wants the asset/image/PDF link, an asset filename, or an asset folder path. Do not use for ordinary page wikilinks (logseq-core / logseq-link-hygiene).

Logseq asset linker

Produce copy-pasteable asset links relative to a page in pages/.

Quick rules

Relative links into assets/ are formed from a typical page location (logseq/pages/somepage.md), so they start ../assets/....
Image link: ![name](../assets/path). File link: [name](../assets/path). Folder link: [name](../assets/folder).
Use file:/absolute/path only when the user explicitly wants a direct file link.
For namespaced assets, convert / → __ (double underscore) in the filename, and sanitize non-alphanumeric chars to _.
Always return the result as a code snippet for easy copying.

Read references/asset-link-construction.md for the full use cases, examples, and the file:/// handling rules.