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.

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::`.

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.

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.

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.

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).

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.

Convert standard Markdown (especially pasted from ChatGPT or similar) into Logseq-Flavored Markdown: nest code blocks inside bullets, fix heading-to-indent levels, drop horizontal rules, convert wide tables to label-value bullets, fix footnotes to URL-only, and replace generic link text. Use when the user pastes non-LFM markdown to import, asks to "convert to LFM", or to clean up an AI-generated dump. For table column alignment use logseq-table-formatter; for baseline LFM rules see logseq-core / logseq-lfm.

Metaskill for Logseq entity work in the active graph: open [[Logseq/Entity]] and [[Logseq/Entity/<Type>]] pages, dedupe, create or update instances per those type rules, infer candidates from journals, help initialize entity pages when asked, and record graph edits in today's journal (Filed / Updated). All type-specific rules live in the graph; this skill does not list entity types or repo companion skills by name. Other skills in a repo may wrap narrow workflows—discover them from the graph, type pages, or the repo's skill layout. Use for: entity exists?, similar entities?, new entity page?, add entities from today's journal?, define or refresh entity types?

Generate and keep in sync the [[Logseq/Flashcard/Review/Favorite]] deck tree from the graph's :favorites (logseq/config.edn). Use when the user asks to build, refresh, or reconcile favorite-driven flashcard decks: an aggregate {{cards (or …)}} deck, a negated background {{cards (not (or …))}} deck, and one scoped {{cards [[Favorite]]}} subpage per favorite. Runs idempotently via the mise file task and preserves the review-history children Logseq appends to {{cards}} blocks. Do not use for ad-hoc card authoring (logseq-flashcard) or non-favorite decks.

Create or maintain Logseq SRS flashcards and first-class Card entity pages in this garden. Use when the user asks to add a flashcard, factor out cards, create or audit Card pages, audit or fix Keyshort flashcards, ensure {{cards}} queries pick up cards, design or debug simple or advanced query expressions for card decks, or convert shortcut notes into review cards. New generic card work uses [[Card]] and [[Logseq/Entity/Card]]; legacy Keyshort audits may still encounter #card / [[card]]. Do not use for non-Logseq decks (e.g. repeater-only formats).

Import and structure a forum post (Cursor Forum, Reddit, Stack Overflow, or other forums) into a Logseq page with title link, metadata, Original Poster / Response / Related / My Notes sections, and site-specific user namespaces. Use when the user pastes a forum thread or asks to capture/import a forum discussion. For person hubs use the logseq-person command and logseq-entity skill. Do not use for blog posts/articles (logseq-import-blog) or non-forum content.

Look up Logseq-Flavored Markdown details beyond the always-on core: footnote syntax, nested fenced code blocks, bold-vs-backtick rendering pitfalls, the singular/plural naming rationale and aliases, the file-name-vs-link reference table, and the logical-vs-on-disk page distinction. Use when formatting footnotes, debugging why a ref/inline-code renders wrong, deciding a page name, or checking whether a page exists before creating a file. Baseline LFM rules live in logseq-core.

Load [[Logseq/Pref]] and linked pages for encode-wide garden preferences (page naming, namespaces, editorial defaults) before creating pages or entity types. Use when aligning new titles with [[Logseq/Pref/Page/Name]], refreshing prefs in-graph, or routing alongside logseq-entity for naming—not for per-entity definitions (those stay on [[Logseq/Entity/<Type>]]).

Log a research question in the Logseq garden under Topic/Q/..., deduplicate against existing ___Q___ pages, add today's journal link, and research an answer (with AI attribution). Use when the user invokes /logseq-question or asks to file, record, or capture a scoped question page. Do not use for non-Q pages, general notes, or entity types other than question—use skill logseq-entity and the relevant [[Logseq/Entity/<Type>]] page instead.

Author or fix Logseq slideshow pages where top-level bullets are section titles (H2) and nested bullets are individual slides with bullet points and a 16:9 image. Use when the user asks to build a slide deck/presentation in Logseq, add slides, or fix slide structure/image sizing. Do not use for ordinary page bullets or non-slide content.

Format markdown tables inside Logseq Flavored Markdown (LFM) pages and journals: bullet-wrapped first row, continuation rows with aligned pipe columns, padded cells for readable plain text, and [[wikilinks]] for graph commands or pages when they exist. Use when adding or fixing tables in pages/*.md or journals/*.md, when the user asks for column alignment, or after editing comparison tables. Do not use to convert wide tables to bullets (skill logseq-convert-md-to-lfm) or for non-Logseq markdown.

Format a YouTube video transcript inside a Logseq page into clean, navigable, timestamped Logseq-Flavored Markdown. Use when the user pastes a raw YouTube transcript, asks to organize/clean up video notes, add clickable {{youtube-timestamp}} headings, or structure a {{video ...}} block's notes. Do not use for non-video transcripts or for general LFM formatting (that is the logseq-lfm skill / logseq-core rule).

Vendor and refresh the Readwise workflow skills (triage, quiz, book-review, …) from github.com/readwiseio/readwise-skills into this garden's .rulesync/skills/, then regenerate. Use when adding, updating, or auditing the vendored readwise skills, after upstream changes, or when bumping the rulesync version in mise.toml. Do not use the `readwise skills install` command or `rulesync import` for this.

Import and structure a forum post (Cursor Forum, Reddit, Stack Overflow, or other forums) into a Logseq page with title link, metadata, Original Poster / Response / Related / My Notes sections, and site-specific user namespaces. Use when the user pastes a forum thread or asks to capture/import a forum discussion. For person hubs use the logseq-person command and logseq-entity skill. Do not use for blog posts/articles (logseq-import-blog) or non-forum content.

Draft a long-form book review from your Reader highlights — synthesizing the book with your broader reading history to generate original arguments

Build a personalized reading profile from your Readwise Reader data, used by triage, quiz, and other skills

Catch up on your RSS feed — highlights up top, full browse below

Visualize your highlights and their connections in an interactive 2D graph

Generate a personal "Now Reading" webpage from your Reader library

Quiz yourself on documents you've recently read to test understanding and retention

Conversational briefing on your recent reading — what you finished, what you highlighted, and what you had to say about it

How to use the Readwise CLI — access highlights, documents, and your entire reading library from the command line

Analyze your reading history and tell you something surprising you don't know about yourself

Triage Reader inbox one doc at a time with personalized pitches

Draft a long-form book review from your Reader highlights — synthesizing the book with your broader reading history to generate original arguments

Build a personalized reading profile from your Readwise Reader data, used by triage, quiz, and other skills

Catch up on your RSS feed — highlights up top, full browse below

Visualize your highlights and their connections in an interactive 2D graph

Generate a personal "Now Reading" webpage from your Reader library

Quiz yourself on documents you've recently read to test understanding and retention

Conversational briefing on your recent reading — what you finished, what you highlighted, and what you had to say about it

How to use the Readwise CLI — access highlights, documents, and your entire reading library from the command line

Vendor and refresh the Readwise workflow skills (triage, quiz, book-review, …) from github.com/readwiseio/readwise-skills into this garden's .rulesync/skills/, then regenerate. Use when adding, updating, or auditing the vendored readwise skills, after upstream changes, or when bumping the rulesync version in mise.toml. Do not use the `readwise skills install` command or `rulesync import` for this.

Analyze your reading history and tell you something surprising you don't know about yourself