mcpbeat Sign in

Pinboard Skill for Claude

> Digital pinboard for quick project notes, reminders, and ideas. Use this skill when the user wants to jot down a note, reminder, to-do, paper to read, idea, or data issue — including phrases like "pin this", "note to self", "remind me to", "add to pinboard", "I need to remember to", "check out this paper", "look into this later", "jot this down", "don't let me forget", or any quick note the user wants saved for later. Also use when the user says "show my pinboard", "what's on my pinboard", "mark X as done", or "clear my pinboard."

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
146
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/aspi6246/Claude-Code-Skills-for-Academics --skill pinboard

The instruction itself

11 sections, as written by the author

Pinboard: Quick Project Notes

A digital pinboard for capturing notes, reminders, and ideas during a

work session without breaking flow. Notes are saved to PINBOARD.md in

the project root.

Adding a Note

When the user drops a note (e.g., "remind me to call Marco about the

data", "check out Spina et al 2026 on orphan wells"), do the following:

  • Auto-categorise the note into one of four categories based on content:
  • To-Do — action items, tasks, things to do, people to contact,

forms to submit, deadlines

  • Papers — papers to read, articles to follow up on, citations

to check, references to find

  • Ideas — hypotheses to test, research ideas, alternative

specifications to try, things to think about

  • Data Issues — variables to investigate, data quality concerns,

sample construction questions, merge problems to check

  • Add the note silently to PINBOARD.md in the appropriate category

section. Include a timestamp. Do not ask for confirmation, category,

or priority — just save it and move on.

  • Acknowledge briefly — one short sentence confirming the note was

pinned. Do not repeat the note back. Do not ask follow-up questions.

Example: "Pinned." or "Added to your pinboard."

Format for each note entry

- [ ] [YYYY-MM-DD] Note text here

Creating PINBOARD.md

If PINBOARD.md does not exist yet, create it with this structure:

# Pinboard

## To-Do

## Papers

## Ideas

## Data Issues

---

## Done

Adding to an existing PINBOARD.md

Append the new note under the correct category heading. Do not reorder

or modify existing notes. If the file exists but is missing a category

section, add the section.

Reading the Pinboard

When the user says "show my pinboard", "what's on my pinboard",

"any notes?", or similar:

  • Read PINBOARD.md
  • Present the contents organised by category
  • Note how many items are in each category
  • Flag any items older than 7 days as potentially stale — these may

have been forgotten or are no longer relevant

  • If the pinboard is empty, say so

Stale item format

When presenting, add a note next to old items:

- [ ] [2026-03-15] Call Marco about the merge issue ⚠️ (3 weeks ago)

Marking Items as Done

When the user says "mark X as done", "done with X", "finished X",

or "completed X":

  • Find the matching item (match on keywords — it doesn't need to be

an exact quote)

  • Move it from its current category to the Done section at the

bottom of the file

  • Change - [ ] to - [x] and add the completion date
  • Acknowledge briefly: "Done."

Format for completed items

- [x] [2026-03-15] Call Marco about the merge issue ✓ completed 2026-04-07

If multiple items match the user's description, ask which one they mean

before marking done.

Clearing the Pinboard

When the user says "clear my pinboard", "clean up the pinboard", or

"archive done items":

  • "Clear done items" — remove everything in the Done section
  • "Clear everything" — ask for confirmation, then reset the file

to the empty template

  • "Clear stale items" — move items older than 14 days to Done

Always ask for confirmation before clearing.

Important Rules

  • Never modify PINBOARD.md without reading it first — append, don't

overwrite

  • Keep the format consistent so the file stays human-readable
  • This is the user's scratchpad — don't editorialize, reorganise,

or "improve" their notes

  • If the user's note doesn't clearly fit one category, default to

To-Do

  • When in doubt about whether something is a pinboard request, it

probably is — err on the side of pinning it

Other skills for the same job

different authors, same section of the catalogue
Gepetto
by softaworks
×2

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

12k tokens
Scientific Problem Selection
by anthropics
vendor ×2

This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".

29k tokens
Scientific Brainstorming
by ComeOnOliver
×2

Research ideation partner. Generate hypotheses, explore interdisciplinary connections, challenge assumptions, develop methodologies, identify research gaps, for creative scientific problem-solving.

7k tokens
Zapier Workflows
by ComeOnOliver
×2

Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.

9k tokens
Scholar Evaluation
by K-Dense-AI
×1

Provide qualitative-first, evidence-traceable developmental review of scholarly works and audit low-stakes research-assessment rubrics with optional local quality controls. Never use for ranking people or consequential decisions.

39k tokens scripts
Brainstorming Research Ideas
by OpenRaiser
×1

Guides researchers through structured ideation frameworks to discover high-impact research directions. Use when exploring new problem spaces, pivoting between projects, or seeking novel angles on existing work.

5k tokens
Parallel Swarm Implementation
by ComeOnOliver
×1

Loop 2 of the Three-Loop Integrated Development System. META-SKILL that dynamically compiles Loop 1 plans into agent+skill execution graphs. Queen Coordinator selects optimal agents from 86-agent registry and assigns skills (when available) or custom instructions. 9-step swarm with theater detection and reality validation. Receives plans from research-driven-planning, feeds to cicd-intelligent-recovery. Use for adaptive, theater-free implementation.

15k tokens
Research Driven Planning
by ComeOnOliver
×1

Loop 1 of the Three-Loop Integrated Development System. Research-driven requirements analysis with iterative risk mitigation through 5x pre-mortem cycles using multi-agent consensus. Feeds validated, risk-mitigated plans to parallel-swarm-implementation. Use when starting new features or projects requiring comprehensive planning with <3% failure confidence and evidence-based technology selection.

15k tokens

How to use it

Copy the folder

Take aspi6246/pinboard from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.