How do I install the Lcp Go Lcpd skill?

Run npx skillmds@latest add majiayu000/lcp-go-lcpd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lcp Go Lcpd safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lcp Go Lcpd?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lcp Go Lcpd free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lcp Go Lcpd?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lcp Go Lcpd by majiayu000 — Agent Skill

Name: Lcp Go Lcpd
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

You are working in the go-lcpd/ module (the reference LCP daemon and tools).

Scope

Module: go-lcpd/
Primary behavior sources:
- Protocol spec: docs/protocol/protocol.md
- WYSIWID design doc (when present): go-lcpd/spec.md (see $lcp-wysiwid-spec)

Development principles

These are the consolidated rules that previously lived in go-lcpd/AGENTS.md:

If go-lcpd/spec.md exists, implementation MUST match the behavior defined there.
Design for robustness. Keep modules aligned with SRP.
Use a ubiquitous language. Keep terminology consistent across code and docs.
Test-first. Prefer TDD when changing behavior.
Run golangci-lint v2. When changing code, run make lint and fix findings.
Use cmp.Diff in tests. Compare expected vs actual with github.com/google/go-cmp/cmp.Diff.
Make logging diagnosable. Logging level MUST be configurable (for example via env vars).
Prefer lnd libraries. Use lnd-provided APIs/libraries before re-implementing.

Go documentation and commenting (house style)

Every function should have a comment describing purpose and assumptions.
Function comments start with the function name (Effective Go), use complete sentences.
Comments in code should explain intent, not restate the obvious.

Workflow

Locate the relevant codepath under go-lcpd/internal/ or go-lcpd/tools/.
If changing protobufs, edit the .proto sources and regenerate instead of hand-editing generated code.
Prefer small, testable changes; add/update unit tests and integration tests as needed.
If you are authoring/changing go-lcpd/spec.md, use $lcp-wysiwid-spec.

Validation (run from `go-lcpd/`)

make gen (only if protobuf / generated code changes)
make test
make lint
make fmt

Optional integration test (regtest):

LCP_ITEST_REGTEST=1 go test ./itest/e2e -run Regtest_LNDPayment -count=1 -v

---name: lcp-go-lcpddescription: Develop the go-lcpd daemon/tools (Go). Follow repo principles (robustness, TDD, lint) and validate with make test/lint/gen.--- You are working in the `go-lcpd/` module (the reference LCP daemon and tools). ## Scope - Module: `go-lcpd/` - Primary behavior sources: - Protocol spec: `docs/protocol/protocol.md` - WYSIWID design doc (when present): `go-lcpd/spec.md` (see `$lcp-wysiwid-spec`) ## Development principles These are the consolidated rules that previously lived in `go-lcpd/AGENTS.md`: 1. If `go-lcpd/spec.md` exists, implementation MUST match the behavior defined there. 2. Design for robustness. Keep modules aligned with SRP. 3. Use a ubiquitous language. Keep terminology consistent across code and docs. 4. Test-first. Prefer TDD when changing behavior. 5. Run golangci-lint v2. When changing code, run `make lint` and fix findings. 6. Use `cmp.Diff` in tests. Compare expected vs actual with `github.com/google/go-cmp/cmp.Diff`. 7. Make logging diagnosable. Logging level MUST be configurable (for example via env vars). 8. Prefer lnd libraries. Use lnd-provided APIs/libraries before re-implementing. ## Go documentation and commenting (house style) - Every function should have a comment describing purpose and assumptions. - Function comments start with the function name (Effective Go), use complete sentences. - Comments in code should explain intent, not restate the obvious. ## Workflow 1. Locate the relevant codepath under `go-lcpd/internal/` or `go-lcpd/tools/`. 2. If changing protobufs, edit the `.proto` sources and regenerate instead of hand-editing generated code. 3. Prefer small, testable changes; add/update unit tests and integration tests as needed. 4. If you are authoring/changing `go-lcpd/spec.md`, use `$lcp-wysiwid-spec`. ## Validation (run from `go-lcpd/`) - `make gen` (only if protobuf / generated code changes) - `make test` - `make lint` - `make fmt` Optional integration test (regtest): - `LCP_ITEST_REGTEST=1 go test ./itest/e2e -run Regtest_LNDPayment -count=1 -v`

Frequently asked questions

Lcp Go Lcpd