SlopScupper
10 crowdincl. 1 critic

annotation-manager

Obsidian plugin to create and query annotations
Open repo on GitHubgithub.com/jsglazer/annotation-manager
TypeScript · ★ 3 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 7 hours ago by jsglazer · last checked 50 minutes ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-11: an Obsidian plugin for inline annotations with a sidebar and Dataview queries, whose README carries a "Made with Claude" badge. 3 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as jsglazer. There's no account to make: SlopScupper only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
Obsidian plugin to create and query annotations
created
2026-05-22 · pushed 2 days ago · 88 commits · 2 contributors
release
1.1.21 · 2026-07-11
languages
TypeScript 53%JavaScript 41%CSS 5%
paperwork
licensereadme 57% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 7 hours ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
cssjavascripttypescript
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: an Obsidian plugin for inline annotations with a sidebar and Dataview queries, whose README carries a "Made with Claude" badge. It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

Annotation Manager

GitHub release License Made with Claude Gemini Flash Antigravity CI CodeQL OpenSSF Scorecard

Annotate text inline in Obsidian, view all annotations for the current note in a sidebar, style them with custom colors, attach freeform tagged comments, and query annotations with Dataview.

View all/some/none of the annotation markup

Documentation (Wiki)

Full documentation is in the GitHub Wiki:

A link to the wiki is also on the plugin's Settings → Annotation Manager → General tab.


What it does

  • Inline annotations — wrap any text in {={parent/child}your note=} to tag it with an identifier
  • Live Preview rendering — delimiters and identifier are hidden; only the annotated text is shown, optionally styled
  • Annotations sidebar — titled "Annotations" at the top; lists the annotations in the note you currently have open, grouped by identifier, with one-click navigation; switches automatically as you move between notes
  • Comments — attach freeform notes with {@your comment@}, independent of annotations; the Add comment command prompts for a tag from the same list as Apply identifier to selection (pick "No tag" for an untagged comment), or tag one explicitly by typing {@{parent/child}your comment@}. Run it with the cursor immediately after an annotation (no space) and it skips the prompt entirely, inheriting that annotation's tag — toggle this with Auto-inherit adjacent tag (on by default) in the Comments settings tab.
  • Comment & annotate — a single command that wraps the current selection as an annotation and inserts an empty adjacent comment sharing the same tag, in one step, relying on zero-space tag inheritance rather than repeating the identifier; shows an alert if no text is selected
  • Comments sidebar — titled "Comments" at the top; lists the current note's comments grouped by tag, with an untagged "No Tag" section (expanded by default; other sections start collapsed) and a search box to filter comments by text, plus the same one-click navigation as the Annotations sidebar
  • Sidebar navigation — entries show the first five words of each annotation/comment; clicking one jumps to it and places the cursor at the start of the marker (no selection)
  • Sidebar quick-toggle buttons — an identical two-row button panel at the bottom of both sidebars: SB switches between the Annotations and Comments sidebars, and the rest fire the visibility/formatting commands directly (A-F/B-V/B-F for annotations, C-V/C-F/B-V/B-F for comments) — hover any button to see the full command name. Each toggle button reflects its current on/off state with configurable On/Off colors (separate for light/dark themes, under Sidebar Format Options at the bottom of the General settings tab) and no longer pops up a Notice when clicked (Command Palette/hotkey use still shows one). Clicking SB briefly flashes it with its own configurable color (light/dark) before switching sidebars. When the current note has no annotations and no comments, every button in the panel — including SB — turns grey (fixed dark-grey background, light-grey text) to signal there's nothing to toggle.
  • Custom styling — the Annotations & Associated Comments grid on the Annotations settings tab defines colors per identifier or wildcard pattern: separate bracket and text colors (foreground and background, each with its own enable checkbox) for light and dark themes, plus a per-row font size, a live example, a Use checkbox to disable a row without deleting it, and a Del button that asks for confirmation before deleting the row. Each identifier's name is an editable field — rename it in place and the row's colors follow (blank, duplicate, or unsafe names are rejected). Tagged comments reuse the same identifier styles. Styles saved by older versions are migrated automatically.
  • Hex color entry — every color cell in the settings grids (identifiers, unassociated comments, and the sidebar buttons) pairs the swatch with an editable #rrggbb hex field, so you can type or paste an exact color instead of relying on the OS color picker's mode; the swatch and hex field stay in sync and setting either one auto-enables that color
  • Annotations & Comments visibility controls — dedicated Settings tabs (and matching commands) to show/hide annotation and comment brackets, formatting, and — for comments — the entire comment; the Comments (unassociated) grid on the Comments tab sets bracket and text colors, independent of tag color and separate for light/dark themes, for comments with no associated tag — so formatting toggles have a visible effect even on untagged comments
  • Dataview integration — annotations are exposed as a cc field on each note's page object

Quick start

The function {={note}converges in O(n log n)=} for all inputs.
This approach {={math/hot}maximizes the posterior=} under the prior.{@double-check this against the 2023 paper@}
  1. Write an annotation using {={identifier}text=} syntax
  2. Add a comment with the Add comment command (pick a tag, or "No tag", from the prompt), or type {@your comment@} directly
  3. Open the sidebars via the ribbon icon or the Show annotations sidebar / Show comments sidebar commands
  4. Add styling under Settings → Annotation Manager → Annotations → Annotations & Associated Comments (the Add identifier control sits below the grid), and adjust what's shown under the Annotations and Comments settings tabs

Notes

  • Tested with the built-in and Minimal themes only
  • Annotations and comments work in both Live Preview and Source Mode
  • Avoid =} inside annotation text, or @} inside comment text — the parser truncates at the first one it finds
  • Do not place annotations or comments inside inline code or fenced code blocks

Written by Claude!

Read the rest on GitHub

Scan report · 2026-09-11
  • Prohibited terms or links
  • Repository eligibility
  • slopscore.md paperwork
  • Content policy
  • Risk review

0 comments

log in to comment.

report this listinglog in to report