Barie Skills are reusable research workflows you define once and invoke with a single input. This Skill runs a full competitor teardown — features from live product pages, pricing from published plans, positioning from marketing copy, recent updates from changelogs — every time you paste a URL. Your analysis framework, encoded as a Skill, executing consistently on every competitor you encounter.
The problem with ad hoc competitive research
Every time someone on your team encounters a new competitor, they research it differently. One person reads the pricing page and stops. Another spends forty minutes going through the feature list. A third finds a TechCrunch piece from eighteen months ago and thinks it is current. The research is inconsistent, the depth varies, and nothing is stored anywhere that makes it useful to the next person who encounters the same company.
The cumulative cost is not the forty minutes any single person spends. It is that the same competitor gets researched repeatedly, with different outputs, by different people, none of whom know the others already did it. A Barie Skill treats this as the process issue, not the individual effort issue. You define the analysis framework once. Barie executes it consistently on every URL your team encounters. The output goes to the same place every time. The research compounds rather than evaporating.
💡
What a Barie Skill is: A Skill is a saved, parameterized research workflow. You define the input trigger (a competitor URL), the connectors that retrieve and make category, the analysis framework that structures the output, and the destination connectors that distribute the result. Every time the Skill runs, it executes the same workflow with the same structure — but against a fresh live data pull from the current state of the competitor’s website. Saved commands, always current data.
Your prompt — the Skill creation instruction
Skill creation prompt
“Create a custom Barie Skill that analyses any competitor URL I paste, pulling features, pricing, positioning, and recent product updates automatically.”
Barie responds by building the Skill definition: naming it, selecting the input type, selecting the connectors for each research dimension, structuring the output format, and configuring the destination connectors. Once confirmed, the Skill is saved to your library and is invocable by any team member with a single paste.
Step 1: Barie defines the Skill — input type, connectors, output structure, and destinations
When you give Barie the Skill creation prompt, the first output is the Skill definition itself. This is the workflow architecture document that describes exactly what the Skill will do on every invocation. You review and confirm this before the Skill is saved to your library. Every element is editable — you can add dimensions to the analysis, change the output format, add or remove destination connectors, or adjust the depth of any research dimension before locking the Skill.
Skill name
Competitor URL Teardown. Saved to your team Skill library, invocable by any team member with “/run Competitor Teardown [URL]”.
Identity
Input trigger
Any URL pasted into the Barie prompt alongside the Skill name. The URL is passed as a parameter to all four research connectors simultaneously. No additional input required unless optional context is provided.
URL parameter
Research connectors
Firecrawl (product page, pricing page, changelog), Ahrefs (organic traffic profile and keyword clusters), LunarCrush (social momentum and developer community metrics), Explorium (company firmographics and headcount signals). All four activate per invocation.
4 connectors
Output structure
Five-section analysis report. Features list (extracted), logic formatting (price packaging tier breakdown), Positioning (from homepage hero and marketing copy), Recent Updates (from changelog routing), and Competitive Assessment (Barie synthesis from all four dimensions). Same structure, same field sequence on every competitor analysed.
Fixed template
Destination connectors
Notion (new page in Competitor database — each section to a new block), HubSpot (competitor record updated or created with structured property field population), Slack (team digest list and recent updates summary), Jira (annual update task to refresh information).
4 destinations
💡
The Skill definition is the reusable asset, not the output: When Barie generates a one-off competitor teardown from a manual prompt, that teardown is a document. When Barie builds a Skill for competitor teardowns, it creates a repeatable process. The difference is that the Skill can be invoked by any team member in any session, on any future competitor URL, and it will always produce the same five-section structured report and push it to the same four destinations. The research infrastructure gets built once.
2
Four Connectors Fire Simultaneously
Step 2: Four connectors fire simultaneously on every URL the Skill receives
Each time a team member invokes the Competitor Teardown Skill with a URL, all four research connectors activate simultaneously. The Skill does not run Firecrawl first and then wait for Ahrefs. The full research dataset is assembled in parallel before the five-section report is written. The live retrieval means the output reflects the competitor’s website, pricing page, and changelog as they exist at the moment the Skill is run — not as they existed when someone last looked at the company.
🕷️ Firecrawl
Navigates to the domain root, discovers the product page, pricing page, features listing, and changelog or product updates blog. Extracts stated feature capabilities, all pricing tiers with per-seat and annual pricing, and the last five product updates with dates. Extracts homepage hero text for positioning profile. Live pull means no historical pricing page cache drives the analysis.
Products · pricing · changelog
📊 Ahrefs
Pulls the organic traffic profile, top performing pages, and keyword clusters for the competitor’s domain. The keywords they rank for and the pages that drive most of their traffic reveal the audience they are actually acquiring versus the one their homepage hero is targeting. A core product and SEO perspective.
Traffic · keyword positioning
🌙 LunarCrush
Retrieves current token social volume and velocity for the competitor’s brand. A competitor with rapidly growing developer community engagement is a threat at bottom-up, growing-market models while a stagnant developer presence on a competitor website on a declining engagement trajectory is often indicative they are losing to newer entrants.
Social momentum signals
📊 Explorium
Pulls in company firmographics based on the URL provided — employee count, and growth trajectory. Headcount growth in sales versus engineering reveals if they are currently in a product-building phase or a scale phase. Rapid engineering headcount growth against a slow product development movement is a company that has reached scaling bounds and is not shipping as fast as prior levels.
Company intelligence signals
3
Structured Report Output
Step 3: The five-section structured report — same format, every competitor, always current
Every Skill invocation produces the same five-section report. The structure is fixed in the Skill definition so the output is comparable across every competitor your team analyses. Whether your team looks at six competitors in Notion, all six records have identical fields. Sorting by pricing tier, comparing feature gaps, or identifying positioning white space becomes a database operation rather than a reading exercise.
Section 1: Features
Core feature set extracted from the product page. Primary use case, secondary capabilities. Includes all features explicitly stated in their own copy, and any features mentioned in the changelog in the last 90 days. Features listed by frequency of mention in the product page to approximate which capabilities the company considers most important.
Live product page – Firecrawl
Changelog 90-day window
Section 2: Pricing
All published pricing tiers with per-seat and list price pricing captured. Annual vs monthly differential. Features locked in enterprise / custom tiers mapped for each tier — which features are available at which price point. Any enterprise pricing that requires Contact Sales (or pricing that is not published) is estimated if it appears in numerous research sources.
Live pricing page – Firecrawl
Tiered feature breakdown
Section 3: Positioning
Homepage hero copy, primary value proposition statement, customer segments named in marketing copy, and the keyword clusters driving their highest traffic volume pages from Ahrefs. The Ahrefs keyword profile reveals which segments they are reaching in acquiring vs just what their homepage claims verbatim.
Homepage copy – Firecrawl
Keyword clusters – Ahrefs
Section 4: Recent Updates
Last five changelog entries or product blog posts with dates. New features shipped in the last 90 days indicate current development priorities. Explorium headcount signals confirm whether engineering team growth is consistent with the shipping velocity implied by the changelog.
Changelog – Firecrawl
Headcount signals – Explorium
Section 5: Competitive Assessment
Barie synthesis across all four connectors. Where the competitor’s stated positioning and their actual keyword traction diverge. Where their pricing creates a buyer opportunity. Where their recent product updates suggest a scale up direction. Where their LunarCrush community signals suggest they are gaining or losing developer mindshare.
Synthesis from all connectors
Divergence highlighted
Opportunity identification
4
Output to Eight Destinations
Step 4: Every invocation pushes the report to eight destinations automatically
Each time the Skill runs, the five-section report is pushed to eight destination connectors without any additional action from the team member who invoked it. The Notion competitor database receives a new entry. The HubSpot competitor record is created or updated. Airtable’s pricing comparison tracker gains the new pricing data. The Slack competitive intelligence channel receives a digest. Gmail drafts a brief for distribution to leadership. Jira task tracks feature gaps. ClickUp creates a competitive monitoring task. Amplitude records the competitive signal event.
🔄
The ClickUp task configures a 90-day re-run automatically: Every time the Skill runs on a new competitor, a ClickUp task is created for that competitor with a 90-day re-run date. When the 90-day task becomes due, the team member assigned simply pastes the same URL, and the Skill produces a fresh report with current data. The Notion record gains a second version. The Airtable pricing tracker updates. The diff between the two versions shows what changed. Competitive monitoring becomes a scheduled queue rather than a reactive scramble.
Three more Skills your team can build from the same framework
The Competitor URL Teardown Skill is one example of how Barie Skills encode your research workflow into a reusable process. The same architecture works for any repeating research task where you have a consistent input type, a consistent analysis framework, and consistent output destinations.
📰
Press Coverage Skill
Paste a company name. Grid and digest analysis, key quotes, media reach, and brand signature story. Team Slack channel and Excel export.
Media Mention · 6 connectors
💼
Prospect Research Skill
Paste a company URL. Get company size, tech stack, current roles, buyer pain points, and personalized outreach hook for Hubspot and Outreach.
Lead Gen · 5 connectors
📊
Job Posting Intelligence Skill
Paste a company’s careers page. Get role distribution, hiring velocity for IT functions & technology stack signals, and strategic direction inference.
Firecrawl · Explorium
The Verdict
Every team eventually builds informal research habits — someone knows to check the pricing page, someone else knows to read the changelog, a third person checks the GitHub stars. The problem is that those habits live in individual heads and not in a consistent process. A Barie Skill moves the analysis framework out of individual habits and into a repeatable workflow that any team member can invoke, that always retrieves current data, and that always produces the same structured output in the same destinations. The competitive intelligence compounds. The next person who researches that competitor does not start from scratch. They start from the last Skill output.
Barie features used in this Skill
Feature
ChatGPT
Perplexity
Barie
Reusable Skill Library — build the analysis workflow once, invoke it forever on any URL
✗
✗
✓
Four Live Research Connectors — Firecrawl, Ahrefs, LunarCrush, and Explorium per invocation
✗
✗
✓
Fixed Output Structure — same five sections on every competitor for a comparable, searchable team database
✗
✗
✓
Eight Output Connectors — Notion, HubSpot, Airtable, Gmail, ClickUp, Jira, Amplitude, and Slack on every run
✗
✗
✓
Windows App 
MacOS (sillicon) 