From screen recording to portable AI skills: why I built SkillForge

Most browser automation tools are good at replaying one workflow in one product stack. That is useful, but it is also limiting. I wanted something more portable: record a workflow once, extract the steps into a reusable SKILL.md , and let different agents use it later. That is why I built SkillForge . The problem with “watch this Loom and figure it out” A lot of team knowledge still lives in screen recordings, SOP docs nobody updates, and one operator who knows the exact clicks. That breaks fast. New teammates improvise steps AI agents get vague instructions instead of structured workflows Browser automations become brittle and tool-specific The same process gets re-explained over and over A recording is evidence, but it is not yet reusable operational knowledge. What SkillForge does differently SkillForge turns a screen recording into a structured skill that can be reused. The key idea is simple: Record your screen → AI extracts a reusable SKILL.md → any AI agent can replay it That ma