freenet
Review Skills published by freenet, their source repositories, maintenance signals, and identity status.
- Skills
- 5
- Repository stars
- 23
- Identity status
- Source-linked
Provenance
Source and identity
- Profile type
- Creator
- Canonical name
- freenet
- Public sources
- 1
- License context
- LGPL-3.0
Source entries
Agent Skills from freenet
Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.
freenet/freenet-agent-skills
dapp-builder
Build and maintain decentralized applications on Freenet using river as a template. Guides through designing contracts (shared state), delegates (private state), and UI, and through upgrading a live dApp safely. Use when user wants to create a new Freenet dApp, design contract state, implement delegates, build a Freenet-connected UI, OR upgrade an existing dApp — bump freenet-stdlib, ship a new contract/delegate version (v2), fix a bug that re-keys the WASM, or migrate state across a contract/de
freenet/freenet-agent-skills
local-dev
Set up and manage local Freenet development environments and interact with a running node. Use when the user wants to test contract changes locally, debug UI issues, run a local node, query connections/diagnostics, inspect the dashboard, use the WebSocket API, or iterate on a Freenet application without deploying to the live network.
freenet/freenet-agent-skills
pr-creation
Guidelines for creating high-quality Freenet pull requests. This skill should be used when creating PRs for freenet-core, freenet-stdlib, or related repositories. Emphasizes quality over speed, thorough testing, and proper review process.
freenet/freenet-agent-skills
pr-review
Executes a risk-tiered, multi-perspective PR review — triages the change, runs specialist subagents in parallel (code-first, testing, skeptical, big-picture) plus an external model pass scaled to risk, then posts a consolidated review to the PR.
freenet/freenet-agent-skills
systematic-debugging
Methodology for debugging non-trivial problems systematically. This skill should be used automatically when investigating bugs, test failures, or unexpected behavior that isn't immediately obvious. Emphasizes hypothesis formation, parallel investigation with subagents, and avoiding common anti-patterns like jumping to conclusions or weakening tests.
Pinned paths
Every entry links to a specific source path and commit when available.
Repository context
Activity, license, and repository-level popularity are shown as context.
Open the source
Inspect the public repository