Skills enact-hello-go
📦

enact-hello-go

v1.0.2 Content revision r1 Safe ⚡ Contains scripts⚙️ External commands

Run a Go Greeting Example

Developers need a small working Enact skill to verify local setup and learn the package format. This skill runs a Go greeting command with a name input and shows a simple structured tool pattern.

Supports: Claude Codex Code(CC)
🥈 81 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "enact-hello-go" from https://skillstore.io/skills/enactprotocol-enact-hello-go.md and its manifest at https://skillstore.io/api/skills/enactprotocol-enact-hello-go/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/enactprotocol-enact-hello-go.md Signed manifest GET /api/skills/enactprotocol-enact-hello-go/manifest Signed lockfile GET /api/skills/enactprotocol-enact-hello-go/lockfile

Test it

Using "enact-hello-go". Name is Alice.

Expected outcome:

The skill returns a friendly greeting for Alice and reports the Go version used.

Using "enact-hello-go". No name is provided.

Expected outcome:

The skill uses World as the default name and prints the runtime version.

Security Audit

Safe
v4 • 7/5/2026 Open versioned report

Both static detections are false positives in context. The Go import block is normal Go syntax, and the flagged shell text is a documentation code fence showing how to run the example.

2
Files scanned
52
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚡ Contains scripts (1)
hello.go:3-7
⚙️ External commands (1)
SKILL.md:32-34
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/enactprotocol-enact-hello-go/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/enactprotocol-enact-hello-go/security.svg)](https://skillstore.io/skills/enactprotocol-enact-hello-go?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/enactprotocol-enact-hello-go?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/enactprotocol-enact-hello-go/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/enactprotocol-enact-hello-go.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

EnactProtocol. (2026). enact-hello-go security audit report (audit version 4) [Author version 1.0.2]. Skillstore. https://skillstore.io/skills/enactprotocol-enact-hello-go/audits/4

BibTeX citation

@techreport{enactprotocol-enactprotocol-enact-hello-go-2026, author = {EnactProtocol}, title = {enact-hello-go security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/enactprotocol-enact-hello-go/audits/4}, note = {Author version 1.0.2} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "enact-hello-go security audit report (audit version 4)" version: "1.0.2" type: report authors: - name: "EnactProtocol" date-released: "2026-07-05" url: "https://skillstore.io/skills/enactprotocol-enact-hello-go/audits/4" identifiers: - type: other value: "skillstore:enactprotocol-enact-hello-go:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
100
Maintainability
85
Content
69
Community
91
Spec Compliance

What You Can Build

Verify Enact Setup

Run a small Go skill to confirm that Enact can execute a local example.

Learn Skill Structure

Review a compact SKILL.md and Go file to understand basic input, output, and command fields.

Test Tool Integration

Use a predictable greeting response when checking Claude, Codex, or Claude Code workflows.

Try These Prompts

Run the Default Greeting 
Use enact-hello-go with the default name and show me the greeting.
Greet a Specific Person 
Run enact-hello-go with the name Alice and summarize the result.
Explain the Skill Layout 
Explain how enact-hello-go connects its input schema, command, and Go source file.
Adapt the Example 
Use enact-hello-go as a reference and describe how to extend it with one additional string input.

Best Practices

  • Use simple names when testing the command input.
  • Review SKILL.md before adapting the example for another language.
  • Keep demo changes small so output remains easy to verify.

Avoid

  • Do not use this example as a production command runner.
  • Do not pass secrets or private data as the greeting name.
  • Do not expect it to compile or manage larger Go modules.

Frequently Asked Questions

What does this skill do?
It runs a small Go program that prints a greeting and the Go runtime version.
Which tools can use it?
The report lists support for Claude, Codex, and Claude Code.
Does it make network requests?
No. The reviewed files show local command execution only.
Can I change the greeting name?
Yes. The skill defines a name input with World as the default.
Is this a complete Go development assistant?
No. It is a compact example for learning and testing Enact skill execution.
Why does it print the Go version?
The Go program prints the runtime version so users can see which Go environment ran the example.

Developer Details

License

MIT

Author version

v1.0.2

Skillstore revision

r1

Repository

https://github.com/EnactProtocol/enact/tree/main/examples/hello-go

Ref

30c73eac2afe762f6aa9c4553158769369d47351

Maintenance freshness

7/18/2026

Usage

4 downloads · 106 views

File structure

📄 hello.go

📄 SKILL.md