AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Plugin

skill-alessiomarcone-agent-fieldbook-plugin · by alessiomarcone

Designs, packages, validates, and prepares distributable plugins containing skills and optional supported extensions. Use when the user asks to build, migrate, publish, install, distribute, or troubleshoot a Claude Code, Cowork, ChatGPT, or Codex plugin or marketplace; not for creating one standalone skill.

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-alessiomarcone-agent-fieldbook-plugin

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Plugin? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Plugin

Resolve the product and distribution surface before writing any manifest.

References

Read only the selected product branch:

  • Claude Code: references/claude-code-plugins.md.
  • Claude Cowork: references/plugin-building.md.
  • Codex: references/codex-plugins.md.

Procedure

  1. Identify target product, installation model, namespace, and public or private distribution path.
  2. Inventory only required capabilities: skills, agents/subagents, hooks, MCP/connectors/apps, or supported assets.
  3. Prefer several focused skills with explicit handoffs over one broad workflow.
  4. Keep every declared component inside the distributable boundary.
  5. Use only fields supported by the selected product's current schema.
  6. Document install, direct invocation, permissions, provenance, update, and uninstall behavior.
  7. Validate source and packaged artifact; install in a clean environment; test direct and contextual activation.
  8. For public submission, prepare the exact listing, legal, safety, and reviewer materials required by that ecosystem.

Output contract

Return:

  1. Target — product, installation model, namespace, and distribution path.
  2. Architecture — component tree and reason for each component.
  3. Files — ready-to-use manifests and components when implementation is requested.
  4. Install and invoke — exact current commands.
  5. Release gate — validation, clean install, permissions audit, tests, and versioning.

Boundaries

  • Do not mix fields from different plugin ecosystems.
  • Do not activate for creation or revision of a single standalone skill; route that work to skill.
  • Do not declare components without their companion files.
  • Do not claim commands, UI paths, or submission requirements without current official support.
  • Do not distribute credentials, private data, raw transcripts, or unlicensed material.
  • Answer in the user's language.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML