Playbook · Skills and craft¶
You are here: Skills and craft · Power user
Next: Operate agents
Choose one skill and one engine from the catalogs. Review them. Make one small artifact.
| Path | Power user |
| Time | About an hour, plus whatever the renderer needs |
| You need | Creative toolkits |
| Produces | A reviewed choice, and one short artifact or a written rejection of the pack |
1. Name the artifact before the tool¶
Write one sentence: "A 10-second title card for agentsphere," or "One scroll section with a headline and a diagram." If you cannot name it, you are collecting tools.
2. Pick from the lists, narrowly¶
| Job | Pick | Leave |
|---|---|---|
| Motion | One engine (the post groups HyperFrames, Remotion, GSAP, Motion, Lottie) and one skill | The other eighteen names |
| A website section | scrolltide.co or one link you open from the source post | The other nine, until this one has taught you something |
The names and the unresolved links are on the concept page. Only claude-motion was resolved for the motion list.
3. Review before install¶
Answer on a note, from the files, not from the README's adjectives.
| Question | Answer you can accept |
|---|---|
| What does the install command execute? | You read it |
| Which commit will you pin? | A specific revision |
| What tools does the skill tell the agent to call? | A list you would show a teammate |
| Does any line tell the agent to ignore other instructions? | If yes, stop |
| Does the environment you will use contain production keys? | It should not |
| What is the renderer, and where does the output file go? | You can point at both |
The motion post says to check each repo before you install (@N01ennn, per post). This table is the check. More context: supply chain.
4. Write a small brief¶
Artifact: 10-second title card.
On screen: the word Agentsphere, the tagline AI AGENTS REPOSITORY, and the robot mark.
Skill: the one you reviewed.
Engine: the one you reviewed.
Checks: duration, readable type on a dark ground, no extra logos.
Done when: a file exists and you have watched it.
Put the brief in a file. Point the agent at the skill. Keep your standing rules in the system prompt, not inside the brief.
5. Watch the trajectory¶
| Keep | Rework |
|---|---|
| It followed the skill's checks | It invented a second framework halfway |
| The output is the file you named | The output is a description of a file |
| You can see timing or layout decisions | The prompt was only "make it premium" |
If the pack fails the review in step 3, the artifact for this playbook is the rejection note. That counts. You practiced the gate.
Check yourself¶
- How many engines are you allowed to add before the first artifact exists?
- Which motion URL is linked from this guide without opening the post?
- What is a successful outcome if the skill tells the agent to ignore its other rules?
Sources¶
- @N01ennn and @himanshubuildss, per post.
- The review table and the brief are synthesis.
Continue¶
Map | Paths | Glossary | References