Conversation
| "name": "Radius Technology Systems" | ||
| } | ||
| }, | ||
| "homepage": "https://github.com/radiustechsystems/radius-cli/tree/main/plugins/radius", |
There was a problem hiding this comment.
We probably should have a page either on the docs or www that acts as this projects homepage.
|
|
|
||
| ```sh | ||
| claude plugin marketplace add radiustechsystems/radius-cli | ||
| claude plugin install radius-dev@radius-cli |
There was a problem hiding this comment.
Still don't love this naming convention.
There was a problem hiding this comment.
/plugin marketplace add radiustechsystems/tools
/plugin install radius@skills
It would require this monorepo be renamed to "tools"
There was a problem hiding this comment.
I'm supportive of this rename. Is @radius available in skills marketplaces?
There was a problem hiding this comment.
Within this setting "radius" is not part of a global namespace so should be fine
| const key = process.env.RADIUS_PRIVATE_KEY; | ||
| if (!key) throw new Error('Configure RADIUS_PRIVATE_KEY through your secrets manager'); | ||
| const signer = privateKeyToAccount(key as `0x${string}`); | ||
| const wallet = createRadiusFetch({ |
There was a problem hiding this comment.
We may want a generic fetch that can just answer whatever the seller provides. I started down a path of making the SDK more multi-EVM compatible #40 but am holding off until we can discuss.
2 participants
I also made a few comments throughout for further consideration.