Harry Toolkit

English ｜ 繁體中文

Requires Obsidian 1.8.7 or later.

A personal toolkit for Obsidian that bundles a few small, self-contained tools for writers. Every feature can be turned on or off individually in settings — a disabled feature adds no commands, no views and no notices.

All data lives inside your vault, as note frontmatter, plain Markdown and JSON files. Everything remains readable if you disable or remove the plugin.

Network use: only the Threads analytics feature connects to the internet. It calls Meta's official Threads API to read your own account's data. It never posts. Every other feature is fully offline.

Scrolling

While drafting or proofreading a long document, the cursor stays at a fixed position on screen and the text flows past it line by line — your eyes don't have to chase the cursor and your hands never leave the keyboard. Similar to typewriter mode, but you control the pace.

Two commands, bindable under Settings → Hotkeys (search for "Harry Toolkit"):

• The cursor's on-screen position never moves; its document position follows, so you can start editing at the new spot immediately
• Hold the hotkey to scroll continuously, or tap it to move line by line
• Wrapped lines are measured correctly, and the target column is preserved so the cursor doesn't drift sideways when passing short lines
• At the top or bottom of the document the cursor simply settles on the first or last line
• Works in Source mode and Live Preview; Reading mode has no cursor, so it doesn't apply
• Works on both desktop and mobile

Settings

• Lines per scroll — how many lines one keypress moves (default 1, max 20)
• Smooth scrolling — animate the scroll (off by default; keep it off if you hold the key down)

Publishing calendar

Article scheduling plus a standalone to-do list, for writers. It does not connect to any publishing platform — it keeps track of your plan. The main view is the calendar, opened from the 📅 ribbon icon or the Open publishing calendar command.

The calendar

• Each day shows scheduled articles (blue), published articles (green) and to-dos due that day (purple); overdue items get a red outline. Weeks start on Sunday
• Click empty space in a day cell to add a to-do due that day
• Drag to reschedule: scheduled articles and open to-dos can be dragged to another day. Hovering over the previous/next month arrow for about half a second flips the month, so you can drag across months
• Published articles and completed to-dos can't be dragged
• Hover a scheduled article for a ✓ to mark it published — the publish date is the day cell it sits in, so to backfill an old post, drag it to that day and click ✓
• Hover for an ✗ to unschedule (back to draft) or, on a published article, to revert it to scheduled
• To-dos have a checkbox to complete them, and a pencil button to rename them in place (Enter or click away to save, Esc to cancel)
• Below the grid are three collapsible sections — Unscheduled to-dos, Scheduled items and File browser — each collapsed from its own heading
  • Unscheduled to-dos holds to-dos with no due date; drag one onto a day to give it one
  • Scheduled items is a flat, date-ordered overview of everything upcoming, across months
  • File browser is a folder tree with a file list beside it, so you can browse without leaving the calendar; drafts and pinned notes live here too
• Put the calendar wherever you like — right sidebar, left sidebar or the main editor area. It stays where you put it. Re-running the command reveals the existing calendar rather than opening a second one, and Obsidian restores its position on restart
• Right-click the calendar's tab → Move to new window to pop it out onto a second monitor
• Hover the empty part of a day cell to see every item due that day, with full titles that the narrow cells would otherwise cut off (overdue ones are marked)
• Click the day number to open that day's daily note, creating it if needed (it follows the core Daily notes plugin's format, folder and template settings). Days that already have a note get a small dot
• Drag and drop needs a mouse; on mobile, use the commands or edit the frontmatter directly

File browser

A collapsible section at the bottom of the calendar that lets you browse folders without leaving the calendar — a sidebar can only show one tab at a time, and switching to the file explorer hides the calendar. Like the calendar's other sections it starts expanded; collapse it from its heading, or turn the whole section off in settings.

• Two columns: an expandable folder tree on the left, and only the files of whichever folder you picked on the right
• The tree grows from the vault root (the top row is your vault's own name), so folders with subfolders stay in the left column and the whole structure is visible at a glance
• Three lists that aren't folders sit at the top of the left column (orange icons, with a rule separating them from the folders below). Click one and the right column swaps to it:
  • Pinned notes (N) — every pinned note in the vault, across folders; hover a row for an unpin button, no right-click needed
  • Drafts (N) — right-click any note → Mark as draft and it shows up here, most recently edited first. Drag one onto a day to schedule it and it moves out of the draft list onto that day
  • Scheduled (N) — every scheduled article and dated to-do, soonest first, each row prefixed with its date and weekday and outlined in red when overdue; the checkbox, inline editing, × and drag-to-reschedule all work as they do on a day cell. In this list the filter box matches dates too, so 09-21 shows just that day Notes in any of these lists can still be dragged onto a day to schedule them
• Clicking a folder expands or collapses it and swaps the right column to its files at the same time — no need to aim for the little chevron (click the chevron itself if you only want to expand without changing the right column). Expanded state is remembered across restarts
• ★ is your favourite folders: pick one to jump straight to it — the tree is never narrowed down, it just expands to that folder, scrolls the left column to it and swaps the right column to its files, so its siblings stay in view. Add the current folder from the bottom of the same menu
• The filter box works live as you type and clears when you change folder. It searches the selected folder and every subfolder below it (with the box empty the right column lists just that one level — depth is the tree's job). Matches from a subfolder show their path relative to the current folder, so same-named notes stay distinguishable; pick the vault root and you are searching everything. It matches file names, not note contents — use Obsidian's own search for that
• Next to the filter box is a button showing the right column's current sort order; click it to change it: file name (A→Z / Z→A), modified time (newest / oldest first) or created date (newest / oldest first). Each folder remembers its own — raw material by last modified, finished articles by name — and the choices survive restarts. Set as the default for other folders at the bottom of the menu covers every folder you haven't set individually. Name sorting is numeric-aware, so 20260915 sorts by value. The tree always sorts by name A→Z, since that column is for navigation and a stable order is easier to scan
• The section heading names the folder you are looking at (e.g. "File browser (books)"), so you can tell where you left off even with the section collapsed
• Click a file to open it in the current tab; Ctrl/Cmd-click or middle-click opens it in a new tab. .md files hide their extension; images, PDFs and others show the full name
• Drag any note onto a day cell to schedule it — not just notes already marked as drafts. Non-Markdown files can't go onto a day cell (there's no frontmatter to write)
• Drop a file onto a folder in the left column to move it there, without switching to the file explorer. Non-Markdown files can be dragged too, as can notes listed under Drafts or Pinned notes, and a folder itself can be dragged to move it with everything inside it
  • The move happens as soon as you let go, and a notice says where it went. Obsidian treats a move as a rename, so every link pointing at the file is updated; drag it back if you got it wrong
  • Hovering over a collapsed folder for about half a second expands it, so you can drag all the way down into a subfolder
  • Nothing is ever overwritten: if the target folder already holds a file of that name, the move is refused with a notice
  • The cursor shows a "no drop" sign where a move makes no sense: the folder the item is already in, the dragged folder itself, and anything beneath it
• Right-click a folder in the left column for New note here and New folder here (the vault root row included). You are asked for a name first; the right column then switches to that folder — a new note opens straight away so you can start writing, a new folder is selected so you can start filling it. Nothing is overwritten if the name is already taken
• Right-click a file or folder for Open in new tab, Open to the right, Rename, Duplicate and Delete, followed by items other plugins contribute. Renaming updates every link pointing at the file, and deleting follows your Settings → Files and links → Deleted files preference
• The list has a maximum height and scrolls internally, so a large folder never stretches the sidebar
• The picked folder and sort order are remembered across restarts; if the folder is renamed or deleted, the browser quietly falls back to the vault root

Article scheduling

• Any note can be scheduled. The schedule lives in the note's frontmatter: publish_status (idea / draft / scheduled / published), publish_date (planned), published_date (actual) and an optional platform tag. You never have to write these fields yourself — the actions below do it for you
• Mark this note as a draft puts it in the file browser's draft list, ready to be dragged onto a day. The same action is on the right-click menu of any note (file explorer, tab title, editor menu and links); on a note that is already a draft it becomes Remove draft mark, which clears the scheduling fields and leaves the note as it was
• Schedule this note for publishing opens a date picker; you can set the platform tag at the same time, and it's also on the right-click menu. A note doesn't have to be a draft first
• Mark this note as published sets the status and stamps today's date. To use a different date, click ✓ on the calendar instead
• Scanning can be limited to one folder in settings; leave it empty to scan the whole vault

Pinned notes

• Right-click any Markdown note → Pin note; the same spot offers Unpin afterwards
• Pinning writes pinned: true to the note's frontmatter, and unpinning removes the field, leaving the note as it was. Adding the field by hand works too
• Pinning is not limited by the article scan folder
• Pinned notes are listed under Pinned notes, at the top of the file browser's left column

To-dos

• To-dos are unrelated to articles and live in a Markdown file of your choice (Todo.md by default), in a format compatible with Obsidian's native checkboxes: - [ ] Something 📅 2026-07-10
• Add to-do works without opening the calendar
• Add this note as a to-do prefills a [[link]] to the current note
• Editing the file by hand works; the calendar keeps up automatically

Due reminders

• Checks on startup and hourly, and notifies you about articles and to-dos due today or overdue
• Each item is announced once a day at most
• Check due reminders now runs the check on demand, and reminders can be turned off

Settings

• Article scan folder — empty scans the whole vault
• To-do file — the Markdown file to store to-dos in (created if missing)
• Calendar location — where to open the calendar when it isn't open yet: right sidebar (default), left sidebar, main editor tab or a separate window. An already-open calendar is never moved
• Due reminders — on or off
• Show file browser — whether to include the file browser section
• Favourite folders — one folder path per line, listed in the file browser's ★ menu
• File browser shows Markdown only — hide images, PDFs and other non-note files

Copy as social post

Turns a finished note into plain text you can paste straight into Facebook. It only touches the clipboard — the note itself is never modified.

Facebook drops blank lines when you paste: a note reading "one, blank line, two" arrives as two adjacent lines. It also collapses runs of spaces, and it doesn't understand Markdown, so **bold** shows up with the asterisks. This feature deals with all of that at the moment you copy.

Two entry points (both use the same settings):

• The command Copy as Facebook post — if there is a selection in the editor, only the selection is copied, since a post is often just one section of a longer piece. Bind a hotkey under Settings → Hotkeys
• Right-click a note → Copy as Facebook post (file explorer, tab title, editor menu and link right-click all work)

What the conversion does:

• Strips the frontmatter, so publish_status and friends never reach the post
• Protects blank lines by putting a character on them that is invisible but does not count as whitespace, which stops Facebook collapsing the line. The default is a zero-width space; if that ever stops working, settings offer a braille blank instead
• Protects runs of spaces, so indentation and deliberate gaps survive
• Strips Markdown (optional):
  • **bold**, *italic*, ~~strikethrough~~, ==highlight==, `code` → text only
  • ## Heading → the heading text; #tag is left alone (that's a Facebook hashtag)
  • [text](url) → text (url) — the URL is always kept, since Facebook needs it to build the link preview
  • [[wikilinks]] and [[link|alias]] → the displayed text
  • Lists → a • prefix, flattened (Facebook strips leading whitespace anyway)
  • --- rules → ———
  • Images and %%comments%% are removed entirely — upload images on Facebook itself, and Obsidian comments are private notes to yourself

A notice reports the character count, excluding line breaks and the invisible characters.

Settings: strip Markdown (on/off), blank-line character (zero-width space / braille blank / none), protect runs of spaces (on/off).

Threads analytics

Reads your own Threads post metrics through Meta's official API and shows them as a sortable dashboard inside Obsidian. Post-level metrics only.

Read-only. This feature has no ability to post, and never will.

Getting an access token

1. Create an app of type Threads API in the Meta developer console
2. Find the User Token Generator under the app's Threads API settings
3. When generating the token, tick threads_basic and threads_manage_insights — without the second one you get posts but no metrics. Add threads_read_replies if you also want your replies
4. Paste the token under Settings → Harry Toolkit → Threads analytics and press Test connection

⚠️ The token is stored in plain text, in <vault>/.obsidian/plugins/harry-toolkit/data.json — Obsidian plugins have no access to the operating system's secure storage. If your vault is synced or pushed to Git, the token travels with it. The token is read-only, cannot post, and expires after 60 days, but please weigh that up for yourself.

Tokens last 60 days. The plugin refreshes yours automatically once it has fewer than 10 days left (Meta requires a token to be at least 24 hours old before it can be extended). If one does expire, generate a new one and paste it in.

The dashboard

Open it from the bar-chart ribbon icon or the Open Threads dashboard command.

• Account summary — name, separate post and reply counts, and last-updated time
• Update recent posts — fetch metrics for posts from the last N days (30 by default)
• Refetch everything — fetch metrics for every post
• Sort and search — by views, likes, replies, reposts, quotes, shares or publish date, with full-text search over post content
• Include replies — off by default. This checkbox only controls display; replies have to be fetched first (see below)
• Each row shows its text preview and publish time down to the minute (e.g. 2026/9/17 21:13). The text is clamped to two lines; hover it to see the whole post
• Each row shows six numbers — views, likes, replies, reposts, quotes, shares — with the current sort column highlighted. Click a row to open the post in your browser

How long a fetch takes

Post metrics must be requested one post at a time — the API has no batch endpoint — with a 0.18 s pause between posts to stay within Meta's limits:

Progress is shown throughout and Stop is always available; whatever has been fetched is still saved. Day to day, Update recent posts is enough. Refetch everything asks for confirmation first, with a time estimate based on your post count.

Closing the dashboard tab does not stop a fetch — it runs on the plugin, not the view. Reopening the dashboard reconnects to the same progress. Quitting Obsidian or disabling the plugin does abort it, and since saving happens once at the end, that run is lost.

Refetching never damages existing data

The data file is append-and-update only: posts that weren't queried this round keep their existing numbers. So stopping halfway, individual failures, and repeated refetches are all safe, and posts deleted on Threads stay in your records.

Changing tokens or accounts

Regenerating a token for the same account is transparent — paste it in, test the connection, and your existing data carries on.

The data file records which account it belongs to. If a new token belongs to a different account, you get a warning before fetching, because mixing two accounts' posts into one file makes the rankings meaningless. To track both, point the data folder setting somewhere else, or move the existing posts.json aside.

To start over, delete posts.json and fetch again — post metrics can always be refetched.

Fetching your replies

Replies come from a different endpoint (me/replies, not me/threads), so they're a separate switch:

1. The token needs the threads_read_replies permission
2. Turn on Also fetch my replies in settings
3. Fetch again
4. Tick Include replies on the dashboard

Replies usually far outnumber posts, so fetching takes noticeably longer — hence the default.

The reply-count column shows "—" for replies. That's not a failure: Meta's API returns 0 for reply-type posts regardless of reality, so the number is meaningless. Views, likes, reposts and quotes are all reported normally.

Data files

One JSON file in the folder you choose (Threads 數據 by default): posts.json, holding post content and their latest metrics.

It lives in your vault, not in the plugin folder, so it survives uninstalling the plugin and travels with your backups. It is ordinary JSON you can read or feed to other tools.

What this feature can't give you

• Followers gained per post — not exposed by the official API. The Threads website shows it, but scraping it would need an automated browser, which an Obsidian plugin can't do
• Other people's accounts — the API only covers your own
• Audience demographics and link clicks — available from the API, but deliberately not implemented: demographics need 100+ followers, and link clicks are aggregated per URL at the account level, so they can't be attributed to a post

Settings

• Access token — see above
• Test connection — verifies the token and records the account id
• Data folder — where the JSON file goes (empty means the vault root)
• Days for "Update recent posts" — default 30
• Also fetch my replies — off by default; needs threads_read_replies
• Dashboard location — where to open the dashboard when it isn't open yet

Enabling and disabling features

Settings → Harry Toolkit has one section per feature, each starting with an Enable this feature toggle. A disabled feature's commands, views and notices all disappear; the others are unaffected. Toggling requires a reload to take effect — disable and re-enable the plugin under Community plugins, or press Ctrl+R / Cmd+R.

Installation

From Community plugins

Settings → Community plugins → Browse, search for Harry Toolkit, then Install and Enable.

Manually

Download main.js, manifest.json and styles.css from the latest release into <your vault>/.obsidian/plugins/harry-toolkit/, reload Obsidian with Ctrl+R / Cmd+R, and enable the plugin under Community plugins.

Afterwards, bind the two scrolling commands under Settings → Hotkeys (search for "Harry Toolkit").

Development

npm install
npm run dev     # watch and rebuild
npm run build   # production build, writes main.js

Type-check with npx tsc --noEmit.

Project structure

src/
├─ main.ts          entry point: load settings, run the feature list, mount the settings tab
├─ core/            the Feature interface, settings merging, the shared settings tab
└─ features/
   ├─ index.ts      the feature registry — adding a feature means adding one line here
   ├─ scroll/
   ├─ scheduler/    calendar, articles, to-dos, reminders, file browser
   └─ threads/      API client, storage, sync, dashboard

Features never import the plugin class; they receive everything they need through a FeatureContext, so each one can be added or removed without touching the others.

License

MIT