[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV4P9D2GAF28FF7N5BS1X5":3,"skill-same:01M7EV4P9D2GAF28FF7N5BS1X5":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EV4P9D2GAF28FF7N5BS1X5","ams-notion-pro",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-notion-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: notion-pro\ndescription: Master advanced Notion: relational databases, formulas, rollups, templates, automations, and workspace architecture. Use when building or optimizing Notion systems for projects, knowledge, or teams.\ncategory: productivity\n---\n\n# Notion Pro\n\n## Overview\n\nNotion is a block-based workspace where every page can also be a database row.\n\nBeginners make pages; power users build small applications from a handful of interconnected databases.\n\nThe pro move: design a small schema (4-8 databases), link them with relations, and surface them through filtered views.\n\nFormulas, rollups, templates, buttons, and native automations turn those databases into a working system.\n\nMental shift: stop asking 'where should I put this page?' and ask 'which database does this belong to, and which views need it?'\n\nA well-built workspace runs projects, CRM, content pipelines, and meeting notes from one source of truth.\n\n## When to use\n\n- Setting up or restructuring a Notion workspace for an individual or team\n- Designing databases with relations, rollups, and formulas that compute useful state\n- Building dashboards, templates, and button-driven capture workflows\n- Automating repetitive Notion work with native automations or the API\n- Migrating from scattered docs and spreadsheets to one structured system\n- Auditing a workspace that has become slow, sprawling, or confusing\n\n## Core concepts\n\n- **Databases, not pages.**\n  One Tasks database with Kanban, calendar, and 'my week' views beats five separate task lists that drift out of sync.\n- **Relations and rollups.**\n  Link Projects \u003C-> Tasks or People \u003C-> Meetings, then roll up counts, sums, and latest dates across the link.\n- **Views as interfaces.**\n  Same database, many lenses: Kanban for execution, calendar for scheduling, table for bulk edits, timeline for planning.\n- **Formulas.**\n  Derive status ('Overdue'), scores, progress bars, and auto-titles. Keep them readable; document the clever ones.\n- **Templates.**\n  Pre-fill new rows with checklists, owners, and relative dates so the happy path is the default path.\n- **Buttons.**\n  One-click multi-step actions: create a project with its tasks, log a meeting, move an item through stages.\n- **Native automations.**\n  Trigger on page-added or property-changed: notify in Slack, stamp dates, sync statuses. No third-party tool needed.\n- **Synced blocks and linked views.**\n  Reuse the same filtered view on your home page, weekly review, and team standup page. Edit once, update everywhere.\n- **Permissions as architecture.**\n  Share pages, not the whole workspace. Use groups for teams, guests for externals, and lock schemas once stable.\n\n## Practical workflow\n\n1. **Map the schema on paper.**\n   List entities (projects, tasks, notes, people) and their relationships. If it doesn't fit one page, it's too complex.\n2. **Build core databases minimally.**\n   Start with title, status, owner, dates, relations. Add properties only when a real workflow demands them.\n3. **Wire relations, then rollups.**\n   Add the links first, then the aggregates you actually check in reviews: open counts, totals, completion %.\n4. **Design daily views.**\n   Create the 2-4 views you'll open every day. Name them by job ('This week's focus'), not by view type.\n5. **Add database templates.**\n   Meeting notes, project kickoff, bug report, content brief — each with pre-filled structure and checklists.\n6. **Build one home dashboard.**\n   Linked views filtered to 'me + this week', capture buttons, links to full databases. Your daily driver.\n7. **Automate the boring parts.**\n   Status transitions, assignment notifications, date stamping, archiving. API only when native automations fall short.\n8. **Set permissions deliberately.**\n   Default-private, share deliberately. Audit guests quarterly, especially on client or HR-adjacent databases.\n9. **Schedule maintenance.**\n   Monthly: archive done items, merge duplicate tags, fix broken relations. Quarterly: does each database still earn its place?\n\n## Common pitfalls\n\n- **Database sprawl.**\n  Twenty micro-databases with no relations is worse than one spreadsheet. Consolidate aggressively.\n- **Over-formula-ing.**\n  Clever formulas nobody understands become maintenance debt. Simple and readable wins.\n- **No archive strategy.**\n  Stale rows slow everything. Add an Archived status, filter it from views, archive quarterly.\n- **Templates without defaults.**\n  A template that pre-fills nothing saves no time. Defaults should encode the correct workflow.\n- **Sharing everything.**\n  Default-open workspaces leak. Audit sharing quarterly, especially external guests.\n- **Automating before stabilizing.**\n  Automate only after doing a workflow manually for weeks, or you entrench the wrong process.\n- **Views nobody opens.**\n  Twelve linked views look impressive and get ignored. Three daily views beat twelve decorative ones.\n- **Property creep.**\n  Every 'just in case' property adds friction to every future row. Unused in a month? Delete it.\n","# Notion Pro\n\n## Overview\n\nNotion is a block-based workspace where every page can also be a database row.\n\nBeginners make pages; power users build small applications from a handful of interconnected databases.\n\nThe pro move: design a small schema (4-8 databases), link them with relations, and surface them through filtered views.\n\nFormulas, rollups, templates, buttons, and native automations turn those databases into a working system.\n\nMental shift: stop asking 'where should I put this page?' and ask 'which database does this belong to, and which views need it?'\n\nA well-built workspace runs projects, CRM, content pipelines, and meeting notes from one source of truth.\n\n## When to use\n\n- Setting up or restructuring a Notion workspace for an individual or team\n- Designing databases with relations, rollups, and formulas that compute useful state\n- Building dashboards, templates, and button-driven capture workflows\n- Automating repetitive Notion work with native automations or the API\n- Migrating from scattered docs and spreadsheets to one structured system\n- Auditing a workspace that has become slow, sprawling, or confusing\n\n## Core concepts\n\n- **Databases, not pages.**\n  One Tasks database with Kanban, calendar, and 'my week' views beats five separate task lists that drift out of sync.\n- **Relations and rollups.**\n  Link Projects \u003C-> Tasks or People \u003C-> Meetings, then roll up counts, sums, and latest dates across the link.\n- **Views as interfaces.**\n  Same database, many lenses: Kanban for execution, calendar for scheduling, table for bulk edits, timeline for planning.\n- **Formulas.**\n  Derive status ('Overdue'), scores, progress bars, and auto-titles. Keep them readable; document the clever ones.\n- **Templates.**\n  Pre-fill new rows with checklists, owners, and relative dates so the happy path is the default path.\n- **Buttons.**\n  One-click multi-step actions: create a project with its tasks, log a meeting, move an item through stages.\n- **Native automations.**\n  Trigger on page-added or property-changed: notify in Slack, stamp dates, sync statuses. No third-party tool needed.\n- **Synced blocks and linked views.**\n  Reuse the same filtered view on your home page, weekly review, and team standup page. Edit once, update everywhere.\n- **Permissions as architecture.**\n  Share pages, not the whole workspace. Use groups for teams, guests for externals, and lock schemas once stable.\n\n## Practical workflow\n\n1. **Map the schema on paper.**\n   List entities (projects, tasks, notes, people) and their relationships. If it doesn't fit one page, it's too complex.\n2. **Build core databases minimally.**\n   Start with title, status, owner, dates, relations. Add properties only when a real workflow demands them.\n3. **Wire relations, then rollups.**\n   Add the links first, then the aggregates you actually check in reviews: open counts, totals, completion %.\n4. **Design daily views.**\n   Create the 2-4 views you'll open every day. Name them by job ('This week's focus'), not by view type.\n5. **Add database templates.**\n   Meeting notes, project kickoff, bug report, content brief — each with pre-filled structure and checklists.\n6. **Build one home dashboard.**\n   Linked views filtered to 'me + this week', capture buttons, links to full databases. Your daily driver.\n7. **Automate the boring parts.**\n   Status transitions, assignment notifications, date stamping, archiving. API only when native automations fall short.\n8. **Set permissions deliberately.**\n   Default-private, share deliberately. Audit guests quarterly, especially on client or HR-adjacent databases.\n9. **Schedule maintenance.**\n   Monthly: archive done items, merge duplicate tags, fix broken relations. Quarterly: does each database still earn its place?\n\n## Common pitfalls\n\n- **Database sprawl.**\n  Twenty micro-databases with no relations is worse than one spreadsheet. Consolidate aggressively.\n- **Over-formula-ing.**\n  Clever formulas nobody understands become maintenance debt. Simple and readable wins.\n- **No archive strategy.**\n  Stale rows slow everything. Add an Archived status, filter it from views, archive quarterly.\n- **Templates without defaults.**\n  A template that pre-fills nothing saves no time. Defaults should encode the correct workflow.\n- **Sharing everything.**\n  Default-open workspaces leak. Audit sharing quarterly, especially external guests.\n- **Automating before stabilizing.**\n  Automate only after doing a workflow manually for weeks, or you entrench the wrong process.\n- **Views nobody opens.**\n  Twelve linked views look impressive and get ignored. Three daily views beat twelve decorative ones.\n- **Property creep.**\n  Every 'just in case' property adds friction to every future row. Unused in a month? Delete it.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-notion-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-notion-pro",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-notion-pro",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-notion-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-notion-pro\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]