agentsclimarketplace
Sign in

Research

Skill mj-deving/pai-skills/skills/Beads/Research

Research Beads best practices from primary sources. USE WHEN real Beads documentation, senior-user workflow patterns, architecture drift analysis, or source-grounded Beads doctrine and recommendations are needed.From its SKILL.md

Install
npx -y skills add mj-deving/pai-skills --skill Research

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 367 tokens by cl100k_base, as published. Nobody here has run it

Beads Research

Use this skill when the task is about understanding how Beads is actually used in the wild, not changing one repo yet.

Outcome rule:

  • distinguish current Beads guidance from mixed-era or stale docs
  • prefer primary sources over forum-style summaries
  • turn research into operational recommendations, not a citation dump

Quick start

  1. Read references/source-map.md.
  2. Load only the relevant reference file:
  3. If the user asked for the latest or to verify, re-browse the current Beads docs/README and the cited DoltHub posts before answering.

Core rules

  • Treat current Beads as version-sensitive. State clearly when a conclusion comes from current docs versus older doc pages.
  • When sources disagree, anchor on the current README and current docs, then explain the older model as drift or historical context.
  • Focus on operational questions:
    • embedded versus server mode
    • shared remote versus per-clone remote
    • CLI plus hooks versus MCP
    • formulas, gates, and durable handoff
    • recovery and lock/rehearsal posture
  • If recommending tooling, tie each proposed tool to a concrete failure mode or workflow bottleneck.

Deliverable shape

A good answer from this skill usually includes:

  • what is current
  • what appears mixed-era or stale
  • what senior users optimize for
  • what skills, workflows, or scripts would reduce risk or toil

Do not overquote sources. Summarize them and include links.

What ships with it: 4 files

5.9 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 326,679. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.