Skip to content

import-from-ai: standalone identity, drop permissions/memory pre-reqs - #136

Open
Kyra Richards (kyra-cpu) wants to merge 1 commit into
mainfrom
runneth/import-from-ai-standalone-identity
Open

import-from-ai: standalone identity, drop permissions/memory pre-reqs#136
Kyra Richards (kyra-cpu) wants to merge 1 commit into
mainfrom
runneth/import-from-ai-standalone-identity

Conversation

@kyra-cpu

Copy link
Copy Markdown
Contributor

What

import-from-ai no longer requires add-roles-permissions and no longer calls team-member-memory's whoami resolver scripts. install-config bumped to 1.1.0.

  • The hard prerequisite check (workspace-map.json present, else route to install add-roles-permissions) is gone from SKILL.md, behavior-snippet.md, README, marketing (requires: "Nothing"), install-config requires, and the post-install intro.
  • Identity now resolves from the conversation surface itself: Slack profile email or Motion userEmail, handle = slugified local part, with a one-question fallback when no email is available.
  • Two guards replace the old collision flow: the Phase 4 restate-and-gate now states the handle and path before the first write, and the skill stops rather than writing into a folder that clearly belongs to someone else.

Why

add-roles-permissions and team-member-memory are both hidden from the library while they're reworked (and team-member-memory's resolver swap is still pending in #134). import-from-ai is shown on the site, and a shown card must not dead-end users into installing hidden use cases — today the skill literally stops and routes them there. If add-roles-permissions is installed later, its stricter resolvers govern; handles derived this way stay compatible.

Part of the same cleanup as #135 (brain-onboard). runneth-classic gets its own PR.

🤖 Generated with Claude Code

Removes the add-roles-permissions prerequisite and the
team-member-memory whoami-resolver dependency. Both use cases are
hidden from the library while they're reworked, so import-from-ai must
not require or route users to them. Identity now resolves from the
conversation surface (Slack profile email or Motion userEmail), the
handle and path are confirmed with the user before the first write, and
the skill stops rather than writing into someone else's folder. Bumps
install-config to 1.1.0.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant