Skip to content

peter-gy/agent-plugins / skills/package-agent-plugin

package-agent-plugin

Verified

Package version-matched agent briefings with a Python project. Use when authoring core skills and references, exposing guidance through Python module help, configuring a build adapter, attaching a plugin to a wheel, or verifying installed handoffs. For consuming an installed package's instructions, use agent-plugins.

FileKindSize
SKILL.mdskill md5.6 KB
agents/openai.yamlconfig235 B
references/briefings.mdmarkdown6.8 KB
references/build-variants.mdmarkdown1.8 KB
references/verify-artifacts.mdmarkdown1.9 KB

references/verify-artifacts.md

View on GitHub
# Verify package artifacts

Treat source and installed inspection as two views of the same selected plugin:

```python
import agent_plugins as ap

source = ap.Plugin.from_project(".")
installed = ap.locate("my-package")

assert source.manifest.name == installed.manifest.name
assert [path.relative_to(source.path) for path in source.files] == [
    path.relative_to(installed.path) for path in installed.files
]
```

Verify every release boundary:

1. Run `agent-plugins plan PROJECT` and inspect every selected path.
2. Build a wheel and source distribution through the configured adapter, or
   attach the plugin to the externally built wheel.
3. Rebuild a wheel from the source distribution.
4. Install the direct and rebuilt wheels in clean environments.
5. Run `agent-plugins read my-package` and `ap.read("my-package")` against both
   installed wheels. Pass an explicit skill name when it differs from the
   distribution name. Compare the Python briefing with CLI `--skill` output.
6. Install the project as editable and confirm `locate()` resolves the authored
   plugin root.
7. Compare source and installed file inventories and bytes.
8. Access `manifest.name`, every `skill.source`, and `mcp.servers` when present
   to execute supported document validation.
9. Confirm each `skill.file("SKILL.md")` and referenced resource is selected.
10. Run an Agent Skills validator against every authored skill directory.

Let `AgentPluginError` fail missing configuration, unusable paths, or discovery.
Let `ValidationError` fail invalid manifest, MCP, or skill documents. Artifact
verification should exercise the CLI through the installed console script as
well as the Python API.

When the package exposes module help, inspect its captured output and follow
the [briefing handoff scenarios](briefings.md#verify-the-handoff). Confirm that
each referenced setup or workflow file is available in the installed inventory.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall