Skip to content
Menu

PaulRBerg

AI Agents

Is this your project? Claim and verify →

PRB's collection of agent skills

What HEY knows

Building
Shipping consistentlyShipping: 7 meaningful events in 30 days; latest ship today. Evidence Source

Build Momentum 62How it is measured

Latest ship
Code changes this week (since Mon 19 Oct) · 3 commits · · Code activity

Why it matters: One of 7 meaningful events in the last 30 days: building continued, not a one-off.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts PaulRBerg on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me PaulRBerg’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

HEY can answer 8 of the 11 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 7 meaningful events in the last 30 days, the newest 2026-10-19.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 19 Oct) · 3 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 52 commitsai-skillet 1.0.0+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 19 Oct) · 3 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 52 commitsai-skillet 1.0.0+6 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksGitHubSources

Latest ship

Checked

Code changes this week (since Mon 19 Oct) · 3 commitspaulrberg/dot-agents

Code activitySource linked

What changed, in the repository’s own words:

1 active day in paulrberg/dot-agents.

This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:1c4a5208… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: a week before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about PaulRBerg — as of 2026-10-19

Is PaulRBerg still being built?
DerivedShipping: 7 meaningful events in 30 days; latest ship today. Evidence
What did PaulRBerg ship last?
FactCode changes this week (since Mon 19 Oct) · 3 commits — Code activity, today. Evidence
What does HEY not know about PaulRBerg?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

  1. Code changes this week (since Mon 19 Oct) · 5 commitspaulrberg/agent-skills

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in paulrberg/agent-skills.

    This week HEY looked inside 2 of 5 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes this week (since Mon 19 Oct) · 5 commits (opens in a new tab)

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 52 commitspaulrberg/agent-skills

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in paulrberg/agent-skills.

    This week HEY looked inside 5 of 52 commits to see what changed: 3 changed code, 2 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 52 commits (opens in a new tab)

  3. Code changes, week of 2026-10-12 – 2026-10-18 · 38 commitspaulrberg/dot-agents

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in paulrberg/dot-agents.

    Mostly maintenance or automation — not counted as building. A burst of 38 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 10 of 38 commits to see what changed: 1 changed code, 9 documentation or maintenance only.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 38 commits (opens in a new tab)

  4. 5 releases in paulrberg/agent-skills on 14 Oct

    GitHub release

    Show all 5 releases

    1. ai-skillet 1.0.0paulrberg/agent-skills

      GitHub releaseSource verified

      First release.

      View evidence: ai-skillet 1.0.0 (opens in a new tab)

    2. ai-notify 1.0.0paulrberg/agent-skills

      GitHub releaseSource verified

      First release.

      View evidence: ai-notify 1.0.0 (opens in a new tab)

    3. ai-handoff 1.0.0paulrberg/agent-skills

      GitHub releaseSource verified

      First release.

      View evidence: ai-handoff 1.0.0 (opens in a new tab)

    4. ai-coord 1.0.0paulrberg/agent-skills

      GitHub releaseSource verified

      First release.

      View evidence: ai-coord 1.0.0 (opens in a new tab)

    5. ai-commit 1.0.0paulrberg/agent-skills

      GitHub releaseSource verified

      First release.

      View evidence: ai-commit 1.0.0 (opens in a new tab)

  5. Code changes, week of 2026-10-05 – 2026-10-11 · 66 commitspaulrberg/dot-agents

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in paulrberg/dot-agents.

    Mostly maintenance or automation — not counted as building. A burst of 66 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 10 of 66 commits to see what changed: 1 changed code, 8 documentation or maintenance only, 1 could not be classified.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 66 commits (opens in a new tab)

  6. Code changes, week of 2026-10-05 – 2026-10-11 · 93 commitspaulrberg/agent-skills

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in paulrberg/agent-skills.

    This week HEY looked inside 7 of 93 commits to see what changed: 3 changed code, 3 documentation or maintenance only, 1 could not be classified. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 93 commits (opens in a new tab)

  7. Code changes, week of 2026-10-05 – 2026-10-11 · 2 commitspaulrberg/crypto-registry

    Code activitySource linked

    2 active days in paulrberg/crypto-registry.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 2 commits to see what changed: 2 documentation or maintenance only.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 2 commits (opens in a new tab)

  8. Code changes, week of 2026-09-28 – 2026-10-04 · 47 commitspaulrberg/dot-agents

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in paulrberg/dot-agents.

    Mostly maintenance or automation — not counted as building. A burst of 47 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 10 of 47 commits to see what changed: 1 changed code, 9 documentation or maintenance only.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 47 commits (opens in a new tab)

  9. Code changes, week of 2026-09-28 – 2026-10-04 · 63 commitspaulrberg/agent-skills

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in paulrberg/agent-skills.

    Mostly maintenance or automation — not counted as building. A burst of 61 commits, so HEY looked inside a sample and too few changed code. This week HEY looked inside 10 of 61 commits to see what changed: 1 changed code, 9 documentation or maintenance only. 2 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 63 commits (opens in a new tab)

  10. Code changes, week of 2026-09-28 – 2026-10-04 · 4 commitspaulrberg/crypto-registry

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in paulrberg/crypto-registry.

    This week HEY looked inside 1 of 4 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 4 commits (opens in a new tab)

  11. Code changes, week of 2026-09-21 – 2026-09-27 · 27 commitspaulrberg/dot-agents

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in paulrberg/dot-agents.

    This week HEY looked inside 7 of 27 commits to see what changed: 3 changed code, 4 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 27 commits (opens in a new tab)

  12. Code changes, week of 2026-09-21 – 2026-09-27 · 73 commitspaulrberg/agent-skills

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in paulrberg/agent-skills.

    This week HEY looked inside 3 of 73 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 73 commits (opens in a new tab)

  13. Code changes, week of 2026-09-21 – 2026-09-27 · 1 commitpaulrberg/crypto-registry

    Code activitySource linked

    1 active day in paulrberg/crypto-registry.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 1 commit (opens in a new tab)

  14. Code changes, week of 2026-09-14 – 2026-09-20 · at least 22 commitspaulrberg/dot-agents

    Code activitySource linked

    What changed, in the repository’s own words:

    4 active days in paulrberg/dot-agents.

    This week HEY looked inside 2 of 22 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 22 commits (opens in a new tab)

  15. Code changes, week of 2026-09-14 – 2026-09-20 · at least 30 commitspaulrberg/agent-skills

    Code activitySource linked

    4 active days in paulrberg/agent-skills.

    This week HEY looked inside 6 of 30 commits to see what changed: 3 changed code, 3 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 30 commits (opens in a new tab)

  16. Code changes, week of 2026-09-14 – 2026-09-20 · at least 3 commitspaulrberg/crypto-registry

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in paulrberg/crypto-registry.

    This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 3 commits (opens in a new tab)

  17. Code changes, week of 2026-09-07 – 2026-09-13 · at least 19 commitspaulrberg/dot-agents

    Code activitySource linked

    What changed, in the repository’s own words:

    18 active days in PaulRBerg/dot-agents.

    This week HEY looked inside 1 of 19 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 19 commits (opens in a new tab)

  18. Code changes, week of 2026-09-07 – 2026-09-13 · at least 17 commitspaulrberg/agent-skills

    Code activitySource linked

    19 active days in PaulRBerg/agent-skills.

    This week HEY looked inside 1 of 17 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 17 commits (opens in a new tab)

  19. Code changes, week of 2026-09-07 – 2026-09-13 · at least 1 commitpaulrberg/crypto-registry

    Code activitySource linked

    What changed, in the repository’s own words:

    20 active days in PaulRBerg/crypto-registry.

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 1 commit (opens in a new tab)

  20. Code changes, week of 2026-08-31 – 2026-09-06 · at least 3 commitspaulrberg/dot-agents

    Code activitySource linked

    13 active days in PaulRBerg/dot-agents.

    This week HEY looked inside 2 of 3 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 3 commits (opens in a new tab)

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about PaulRBerg? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

32 changes on HEY’s record for PaulRBerg: 6 releases · 2 build pace changes · 24 weeks of code pushed.

All 32 changes for PaulRBerg →

The full change record holds 2 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 8 of the 11 research questions that apply.

8 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 8m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 5d ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 10h ago.
  • Published packagesMeasuredRead 19m ago.
  • Package advisoriesMeasuredRead 8h ago.

Not applicable here: Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources