Half the apparent gaps are the same skill under a different name
Curricula are reviewed annually, and job adverts change continuously, so a syllabus drifts out of alignment in a way nobody observes until graduates report it.
Comparing them is not keyword matching. Industry names things differently from academia. Tool names substitute for concepts. A module teaching a fundamental skill appears to be absent, even though the advert names a product built on it.
Fashion is the other half of the problem. A tool appearing in adverts for six months is not a curriculum change. Chasing every named technology produces a syllabus with no foundations.
This produces evidence for a curriculum conversation: which requirements appear frequently and are genuinely uncovered, and which are naming differences. The judgment about what to teach stays with the people responsible for the program.
How the ActionFlow runs on the canvas
A Notion or Airtable node holds the curriculum as learning outcomes rather than module titles, which is the level at which a comparison is meaningful.
A Scrappey node and an HTTP Request node gather current adverts for the roles your graduates enter. A Google Sheets node holds the role list.
A Generate Object node extracts requirements from each advert as skills and knowledge rather than as tool names, which is the step that makes naming differences resolvable.
A Math node counts requirement frequency across the advert set, so a requirement appearing twice is not weighted like one appearing in eighty.
A Loop node walks the frequent requirements. A second Generate Object node compares each against the learning outcomes, returning covered, covered under a different name with both named, or genuinely absent.
A Filter node separates those three groups. The renamed group is usually the largest and the most useful. It tells you what to rename rather than what to build.
A Notion node writes the analysis with frequency counts. A Create Excel node produces the table for a curriculum committee.
Nothing changes the curriculum. The output is evidence for the people who do.
Nodes this ActionFlow uses
- Notion (Integration): holds the curriculum as learning outcomes, not module titles.
- Scrappey (Util) plus HTTP Request (Util): gather current adverts for your graduate roles.
- Generate Object (AI Core): extracts requirements as skills rather than tool names.
- Math (Util): counts frequency so rare requirements are not weighted like common ones.
- Loop (Control): compares each frequent requirement against the outcomes.
- Generate Object (AI Core): returns covered, covered under another name, or genuinely absent.
- Create Excel (Data): produces the table for a curriculum committee.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.