Skip to content
Back to skills

Component Make New Actor

ASecurity

Create a new actor component skeleton

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 9, 2026
developmentgit

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add AI-native-Systems-Research/ai-native-storage-certus --skill component-make-new-actor --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Component Make New Actor?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Component Make New Actor
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ai-native-systems-research-component-make-new-actor/badge)](https://www.skillsdirectory.com/skills/ai-native-systems-research-component-make-new-actor)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: component-make-new-actor
description: Create a new actor component skeleton
argument-hint: "[component-name, receptacle-names,...]"
---

Building the skeleton for component named $0 involves the following steps:

1. The interface name is the component name prefixed with the letter 'I'.  The component name is $0, e.g., FooBar is the component name, IFooBar is its interface name.

2. The component should be an actor. It must support an actor channel and provide a method on the interface to open the channels.  Implement a skeleton message protocol along with the interface definition.

3. If it does not already exist, create interface definition file, e.g., ifoobar.rs in components/interfaces directory.

4. Interactively ask if any other interfaces will be provided by this component. 

5. Create a new sub-directory under the components directory.  The name of the directory is a lower-case hyphen-ized version of $0.

6. Implement dummy functions for all provided interfaces.

7. Add recepticals for other interface names specified by other arguments, $1, $2 and so forth.  The receptable must have a corresponding interface defined in src/interfaces.

8. Add a permissions file .claude/settings.json, in the newly created sub-directory, that allows access to the component itself, lib/component-framework and any other directories corresponding to components that are listed as receptacles.  We want to avoid giving access to other components that are not directly used.

9. Copy into the new component directory's `.claude/skills` only the skills whose names match an `include` pattern in `.claude/component-local-skills.json` (patterns support a trailing `*` wildcard; other entries match exactly). This allowlist is the single source of truth for which skills are component-local — do not hard-code the list here. Skip any skill that does not match.

10. Run 'specify init . --ai claude' in the component source directory.

11. Run 'specify extension add spec-kit-sync --from https://github.com/bgervin/spec-kit-sync/archive/refs/heads/master.zip' in the component directory.


Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.