Nov 15, 2026: skills
At some point last week I thought I had published a chronicle, gone to bed, and then didn't notice something wasn't published until I started to work on the next days chronicle. Today, I spent a good bit of time working through some skills that will start to address some of the inconsistencies in cipher's approach to any number of things that burn me here or there. A janky release process is one example that is visible to you dear day one reader, but there are dozens of other examples that I'm going to focus on chipping away at in the coming weeks.
What say you bot:
cipher saysBetter instructions make a more dependable collaborator. AGENTS.md now provides a clearer starting point, with focused skills carrying the details for Jira work, database preparation, and content authoring. Each skill points to its owning documentation, so the agent can find the right procedure without loading every rule into every task.
The guidance makes responsibilities explicit: preserve unrelated work, keep commits tied to the correct story on the shared epic branch, and distinguish prepared work from verified results. Database handoffs stay simple: Cipher prepares the migration and separate ledger file; James executes them. Clearer boundaries help the agent keep moving through authorized work and stop when human execution or approval is actually needed.
lulu learnsThe robot is better prepared to both listen to me and anticipate my needs. Or at the very least it will catch me in my own mistakes before things get too far and a chronicle is missed. Kinda like teaching gully to sit.I've started using claude more at [redacted] so let's let them give the detailed answer on what skills are and how useful they can be at controlling your bot army (very!).
My bot army continues to grow.
cipher says
Tags now distinguish three kinds of connection: membership in a group, alternate names for the same person, and the people who inspire a collection. Each relationship has a direction and a specific meaning; sharing a name does not make two people the same person.
An approved alias points directly to one main identity. Calvin can refer to nephew Cal without creating another person, while Cal Eldrid remains a separate athlete. Links, dated snapshots, search, and Chronicle feeds resolve those alternate references consistently, with duplicate results counted once. Authored display names stay independent, and verified aliases follow the same athlete when their main tag changes.
Collection reasons connect a player or team to the person behind the interest, with explanations such as a shared name or a historical favorite player. Those connections appear separately from family Chronicles and real group memberships; they neither imply card ownership nor add overlapping card counts together. General name categories remain outside this first version.
lulu learnsThere are new ways to link ideas together, like king james and lulu herself. Visit her page and see who I collect because of her as one example.IYKYK
0 archived views from 2025-10-01 through 2026-11-14 UTC; coverage incomplete. Traffic statistics
“skills”; Nov 15, 2026.
Take 2; Day 298, To pay the bills.
Related Chronicles
Take 2; Day 270, Alright, stop, collaborate and listen.
Related by #cardattack, #cipher, #fern, #george, #lulu, #theabbott, #tullyelly, persona: tullyelly
Take 2; Day 276, Man on the moon.
Related by #cardattack, #cipher, #green-beer, #king-james, #theabbott, #tullyelly, persona: tullyelly
Take 2; Day 180, We're all gonna die.
Related by #cardattack, #cipher, #fern, #lulu, #theabbott, #tullyelly, persona: tullyelly
Comments
Loading comments...