actor-model-implementer
Skill17 starsChanged 9 months agoApache-2.0View on GitHub
Implements actor model for concurrent computation. Use when: (1) Building
In this repository98 other files it gives its agents.
- abstract-interpretation-engineSkill
- abstract-machineSkill
- acsl-annotation-assistantSkill
- algebraic-effectsSkill
- alias-and-points-to-analysisSkill
- axiomatic-semanticsSkill
- bidirectional-type-checkingSkill
- bisimulation-checkerSkill
- capability-systemSkill
- closure-converterSkill
- common-subexpression-eliminatorSkill
- concurrency-verifierSkill
- constant-propagation-passSkill
- contextual-equivalenceSkill
- control-flow-analysisSkill
- coq-proof-assistantSkill
- cps-transformerSkill
- dafny-verifierSkill
- dataflow-analysis-frameworkSkill
- dead-code-eliminatorSkill
- defunctionalizationSkill
- denotational-semantics-builderSkill
- dependent-type-implementerSkill
- dsl-embeddingSkill
- effect-handlers-implementerSkill
- effect-systemSkill
- effect-type-systemSkill
- escape-analysisSkill
- existential-typesSkill
- ffi-designerSkill
- fuzzer-generatorSkill
- gadt-implementerSkill
- garbage-collector-implementerSkill
- graalvm-truffle-implementerSkill
- gradual-typing-implementerSkill
- higher-order-abstract-syntaxSkill
- hoare-logic-verifierSkill
- incremental-computationSkill
- information-flow-analyzerSkill
- inline-expanderSkill
- interprocedural-analysisSkill
- invariant-generatorSkill
- jit-compiler-builderSkill
- lambda-calculus-interpreterSkill
- language-server-protocolSkill
- lean-proverSkill
- lexer-generatorSkill
- linear-type-implementerSkill
- liveness-analysisSkill
- llvm-backend-generatorSkill
- lock-free-data-structureSkill
- loop-optimizerSkill
- loop-termination-proverSkill
- macro-expanderSkill
- memory-allocatorSkill
- message-passing-systemSkill
- mlir-dialect-designerSkill
- model-checkerSkill
- module-systemSkill
- monad-transformerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 82
Request-response: - Ask with reply
- Distinctive: line 90
Avoid blocking in actors
- Distinctive: line 91
Use supervision for fault tolerance
- Distinctive: line 92
Consider actor per request for isolation
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Actor Model Implementer
Implements the actor model for concurrent computation.
When to Use
- Building concurrent/distributed systems
- Implementing fault-tolerant systems
- Modeling reactive systems
- Erlang/Elixir-style concurrency
What This Skill Does
- Creates actors - Independent computational entities
- Handles message passing - Asynchronous communication
- Manages mailboxes - Message queuing
- Implements behaviors - Actor state machines
Usage Example
# Create system
system = ActorSystem("example")
# Spawn counter
counter_ref = system.spawn(CounterActor)
# Send messages
counter_ref.tell(10) # Add 10
counter_ref.tell("get") # Query count
# Ask pattern
def on_reply(count):
print(f"Count is: {count}")
# Get reply
future = counter_ref.ask("get")
print(f"Count: {future.result()}")
# Spawn ping-pong
ping = system.spawn(PingPongActor)
pong = system.spawn(PingPongActor)
ping.tell("ping", sender=pong)
# Shutdown
system.stop()Key Concepts
| Concept | Description |
| Actor | Isolated computation with private state |
| Mailbox | Message queue |
| Address | Reference to actor (PID) |
| Message passing | Async, no sharing |
| Behavior | Message handler function |
| Supervision | Fault handling hierarchy |
Actor Patterns
- Fire and forget - Async send
- Request-response - Ask with reply
- Pipeline - Chain actors
- Pub/sub - Topic-based messaging
- Aggregator - Collect results
Tips
- Keep messages immutable
- Avoid blocking in actors
- Use supervision for fault tolerance
- Consider actor per request for isolation
- Monitor mailbox sizes
Related Skills
software-transactional-memory- STM concurrencyrace-detection-tool- Detect race conditionscps-transformer- First-class continuations
Research Tools & Artifacts
Actor model implementations:
| System | Language | What to Learn |
| Erlang/OTP | Erlang | Original actor model |
| Akka | Scala/Java | Production actors |
| Erlang/Elixir | Elixir | Distributed actors |
| Scala Akka | Scala | Typed actors |
| Pony | Pony | Capabilities-based actors |
Papers
- Hewitt, Bishop, Steiger (1973) - Original actor model paper "A Universal Modular ACTOR Formalism for Artificial Intelligence"
- Agha (1986) - "Actors: A Model of Concurrent Computation in Distributed Systems"
- Armstrong - Erlang design papers
Research Frontiers
1. Type-Safe Actors
- Challenge: Message type safety
- Approach: Typed channels, session types
- Tools: Akka Typed, Pony
2. Distributed Actor Frameworks
- Challenge: Location transparency
- Approach: Remoting, cluster management
Implementation Pitfalls
| Pitfall | Real Consequence | Solution |
| Blocking | Mailbox buildup | Async operations |
| Shared mutable state | Race conditions | Immutable messages |
| Deadlocks | System halt | Avoid cyclic dependencies |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

