Distilly (formerly Colleague Skill) builds source-grounded Person Profiles for agents. You pick one of three families, colleague, relationship or celebrity, add source material, review the result, and the skill packages the profile as its own Agent Skill.
It also has an owner flow: a short interview plus the sources your agent already has, saved as a profile and linked into the file your agent reads every session. Generated profiles can be updated with new files, corrected in conversation and rolled back.
What You Get
- A generated Agent Skill per person, stored under skills/colleague, skills/relationship or skills/celebrity in your workspace
- An owner profile saved locally and linked into your agent’s always-on user file
- Append, correct and roll back commands for keeping a profile current
- Collectors that pull messages and documents from Lark, DingTalk and Slack
- A celebrity research pipeline from subtitles to a quality-checked dossier
Common Use Cases
- Keep a departing colleague’s workflow and review style available to the team’s agent
- Build a profile of a public thinker from books and interviews to ask how they would answer
- Tell a new personal agent who you are with a five-minute interview
- Parse exported chat history or email into a profile of a long-time contact
What Makes It Unique
Most persona skills ask for a hand-written description. Distilly starts from source material, ranks which sources count most for each family, and states that the output is grounded in what was observed and does not claim to clone the person. It keeps credentials out of the conversation by having you run setup commands in your own terminal, and it versions every update so a profile can be rolled back.
Under The Hood
SKILL.md lists allowed tools Read, Write, Edit and Bash and routes to prompt files for each flow. The agent runs bundled Python tools through the shell: a skill writer that creates and updates generated skills, parsers for Lark exports and email, and auto-collectors that call the Lark, DingTalk and Slack APIs and a browser session with credentials you set up yourself, stored in the OS keychain or a config file in your home folder. The owner flow looks at files and connector configs on your machine, which you choose from a list, and edits only the marked block of your agent’s user file after showing a dry run. It writes generated skills and knowledge folders in your project, keeps profiles under a folder in your home directory, and can send requests to public sources and a third-party service for celebrity research.