<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: dadev</title>
    <description>The latest articles on DEV Community by dadev (@daviddacruz).</description>
    <link>https://dev.to/daviddacruz</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1400835%2Fdfd06b6f-da32-4cc0-a03f-7906dae6fd65.png</url>
      <title>DEV Community: dadev</title>
      <link>https://dev.to/daviddacruz</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/daviddacruz"/>
    <language>en</language>
    <item>
      <title>Testing the Podcast Ad Response Path: Forms, Promo Codes and CRM Events</title>
      <dc:creator>dadev</dc:creator>
      <pubDate>Wed, 04 Nov 2026 19:43:25 +0000</pubDate>
      <link>https://dev.to/executive-intelligence-ai/testing-the-podcast-ad-response-path-forms-promo-codes-and-crm-events-1obj</link>
      <guid>https://dev.to/executive-intelligence-ai/testing-the-podcast-ad-response-path-forms-promo-codes-and-crm-events-1obj</guid>
      <description>&lt;p&gt;Simplicity Media is a &lt;a href="https://simplicitymedia.com/services/podcast-advertising-agency/" rel="noopener noreferrer"&gt;podcast advertising agency&lt;/a&gt; whose service includes audience planning, creative coordination, placement buying and response measurement.&lt;/p&gt;

&lt;p&gt;A developer supporting podcast marketing usually owns a smaller, testable part of that process: the route from listener interest to a received enquiry. The advertisement may run somewhere else, but the website, code handling and CRM handoff still need acceptance criteria.&lt;/p&gt;

&lt;p&gt;This Executive Intelligence engineering guide proposes those checks. It includes promotional links and illustrative recommendations, not a description of Simplicity Media's internal code or client results. Sources were checked on November 4, 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Define acceptance before adding an analytics event
&lt;/h2&gt;

&lt;p&gt;A response event should correspond to a clearly defined application action. Begin by deciding when the business has actually accepted an enquiry.&lt;/p&gt;

&lt;p&gt;Clicking a form button is an attempt. A successful server response may indicate acceptance. Qualification can happen later in a CRM. Each stage needs its own definition so one event name does not imply the entire journey succeeded.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://developers.google.com/analytics/devguides/collection/ga4/events" rel="noopener noreferrer"&gt;GA4's event setup documentation&lt;/a&gt; explains recording interactions. The application and business teams must still agree the meaning of the interaction being recorded.&lt;/p&gt;

&lt;p&gt;Write acceptance cases for a valid request, a validation failure and a receiving-system failure. State what the visitor should see, which record should exist and which event should fire.&lt;/p&gt;

&lt;p&gt;Then ask the receiving team to confirm that the valid test record is usable. A form that succeeds technically but omits the information needed for follow-up has not completed the intended handoff.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the promo code as business logic
&lt;/h2&gt;

&lt;p&gt;A promo code needs predictable validation and offer behavior. Treat those rules as application requirements rather than a reporting label.&lt;/p&gt;

&lt;p&gt;Check a valid code, an expired code, a mistyped code and a code applied to an ineligible request. The interface should explain the actual condition without suggesting that every failure means the campaign ended.&lt;/p&gt;

&lt;p&gt;Agree how case, whitespace and repeated application are handled. Preserve the original submitted value only where the business needs it and the data-handling design permits it. Keep the normalized reporting value documented.&lt;/p&gt;

&lt;p&gt;If an enquiry can proceed without a code, test that route too. A listener may remember the brand and search later. The application should not require a promotional identifier merely to make reporting easier.&lt;/p&gt;

&lt;p&gt;Include the offer owner in the review. The development team can verify the implementation, while the business must approve the actual eligibility, timing and customer-facing explanation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make repeat requests and failures observable
&lt;/h2&gt;

&lt;p&gt;The handoff should distinguish a retry from a new accepted enquiry according to a documented rule. Otherwise a slow response can inflate the apparent results.&lt;/p&gt;

&lt;p&gt;Test double clicks, network retries, confirmation-page reloads and a returning visitor. Check whether browser and server instrumentation both send a record for the same action.&lt;/p&gt;

&lt;p&gt;Where the application uses an identifier to handle repeat submissions, document its lifetime and which systems receive it. Do not assume a web event identifier also deduplicates the CRM.&lt;/p&gt;

&lt;p&gt;Preserve failure reasons that support investigation. A destination timeout, rejected payload and invalid offer are different operational problems. An aggregate “failed” count may hide the distinction the support owner needs.&lt;/p&gt;

&lt;p&gt;Define the repair process. Someone should know when to pause an affected response route, where to find accepted records and how to verify recovery without resubmitting real customer data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the CRM record and its timestamps
&lt;/h2&gt;

&lt;p&gt;The CRM handoff needs a reliable record, meaningful source fields and unambiguous dates. Trace those values instead of checking only a dashboard total.&lt;/p&gt;

&lt;p&gt;For each test enquiry, verify the receiving record, offer identifier, creation time and assigned owner. Confirm how the CRM represents later qualification and the reason for rejection.&lt;/p&gt;

&lt;p&gt;Document source and reporting timezones. A near-midnight test can reveal differences that an afternoon test misses. Also check delayed updates and whether reporting uses enquiry creation or stage-change date.&lt;/p&gt;

&lt;p&gt;Compare source and receiving-system counts for the agreed cases. If the systems disagree, explain each difference before adding automated reporting.&lt;/p&gt;

&lt;p&gt;Keep this trace as a handoff artifact. Marketing, engineering and sales should be able to use it when a live record appears in one system but not another.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep website QA separate from podcast exposure evidence
&lt;/h2&gt;

&lt;p&gt;A website test verifies the response instrumentation. It does not establish that a particular person heard an advertisement.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://iabtechlab.com/standards/podcast-measurement-guidelines/" rel="noopener noreferrer"&gt;IAB Tech Lab's podcast measurement guidance&lt;/a&gt; distinguishes delivery metrics that come from the podcast environment. Those records need their own source and definition.&lt;/p&gt;

&lt;p&gt;A separate attribution provider may combine delivery and website signals. &lt;a href="https://help.adanalytics.spotify.com/about-attribution" rel="noopener noreferrer"&gt;Spotify's attribution documentation&lt;/a&gt; describes its use of matching, configurable windows and modeled results. Verify what applies to the actual integration rather than assuming one universal method.&lt;/p&gt;

&lt;p&gt;When reviewing the report, label directly recorded events, matched outcomes and estimates. Do not add a household-level association to the website schema as though it were a verified individual viewing history.&lt;/p&gt;

&lt;p&gt;Also keep incremental outcomes separate from credited outcomes. Passing a tracking test cannot validate a causal claim about advertising effectiveness. That requires an appropriate evaluation design.&lt;/p&gt;

&lt;h2&gt;
  
  
  Acceptance questions for the release
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Should the conversion fire on a button click?
&lt;/h3&gt;

&lt;p&gt;Only if the intended metric is the click itself. An accepted-enquiry event should follow the agreed acceptance point.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can the promo code identify every podcast customer?
&lt;/h3&gt;

&lt;p&gt;No. Some people respond without using it. Test the code route and the ordinary enquiry route.&lt;/p&gt;

&lt;h3&gt;
  
  
  How should duplicate handling be approved?
&lt;/h3&gt;

&lt;p&gt;Use a business-approved definition and verify it with concrete test cases. Preserve enough source history to investigate mistakes.&lt;/p&gt;

&lt;h3&gt;
  
  
  What does a stale CRM export mean?
&lt;/h3&gt;

&lt;p&gt;It means the source has not refreshed. Show its age and the missing period instead of replacing unavailable outcomes with zero.&lt;/p&gt;

&lt;h3&gt;
  
  
  Who signs off the response path?
&lt;/h3&gt;

&lt;p&gt;The technical owner verifies implementation, while marketing and the receiving team confirm the offer and operational handoff.&lt;/p&gt;

&lt;h2&gt;
  
  
  Release the trace with the implementation
&lt;/h2&gt;

&lt;p&gt;Hand over the acceptance cases, event definitions, source owners and known limitations with the code. Include one verified test record that can be followed through the receiving systems. That gives the next investigation a concrete starting point.&lt;/p&gt;

&lt;p&gt;For Simplicity Media's current podcast offering, visit &lt;a href="https://simplicitymedia.com/" rel="noopener noreferrer"&gt;simplicitymedia.com&lt;/a&gt; and agree the integration responsibilities before launch.&lt;/p&gt;

</description>
      <category>analytics</category>
    </item>
    <item>
      <title>A Practical Data Contract for CTV Campaign Measurement</title>
      <dc:creator>dadev</dc:creator>
      <pubDate>Wed, 04 Nov 2026 18:54:28 +0000</pubDate>
      <link>https://dev.to/daviddacruz/a-practical-data-contract-for-ctv-campaign-measurement-3n1p</link>
      <guid>https://dev.to/daviddacruz/a-practical-data-contract-for-ctv-campaign-measurement-3n1p</guid>
      <description>&lt;p&gt;A CTV measurement workflow needs shared definitions before it needs another dashboard. Developers, media operators and sales teams should agree what each event represents, where it comes from and how it can be connected to a business outcome. Without that agreement, a technically correct report can still answer the wrong question.&lt;/p&gt;

&lt;p&gt;Simplicity Media's &lt;a href="https://simplicitymedia.com/services/marketing-attribution-agency/" rel="noopener noreferrer"&gt;measurement service&lt;/a&gt; describes reconciling media, web, call and CRM evidence while keeping attribution and incrementality separate. This article turns that principle into a small, illustrative data contract a development team could discuss with its media partner.&lt;/p&gt;

&lt;p&gt;Disclosure: This promotional article discusses Simplicity Media. The schema and workflow are recommendations, not a description of its private systems or a tested integration. Public service information was checked on November 4, 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Define events by the action they actually record
&lt;/h2&gt;

&lt;p&gt;An event name should identify the observed action, while business qualification belongs in a separate field or event. A button click, accepted form and qualified lead are different records.&lt;/p&gt;

&lt;p&gt;For a service website, define a successful submission as the point at which the application accepts the enquiry. Then define how the receiving system marks spam, duplicates, unserviceable requests and valid leads. The analytics layer and CRM should not silently apply different meanings to “lead.”&lt;/p&gt;

&lt;p&gt;&lt;a href="https://developers.google.com/analytics/devguides/collection/ga4/events" rel="noopener noreferrer"&gt;Google's GA4 documentation&lt;/a&gt; distinguishes automatically collected, enhanced measurement, recommended and custom events. Choose the appropriate event type for the implementation, then document the business meaning outside the tag manager as well.&lt;/p&gt;

&lt;p&gt;For each event, record its trigger, source system, timestamp convention, owner and known exclusions. Include whether it fires in the browser, on the server or through an import. Otherwise a migration can change the count without anyone noticing that the underlying definition changed.&lt;/p&gt;

&lt;p&gt;Review failure states with the people handling enquiries. A validation error, network retry or thank-you-page refresh should not create a new qualified lead. Test those cases explicitly because a happy-path submission will not reveal them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep delivery, response and outcomes in distinct records
&lt;/h2&gt;

&lt;p&gt;The data model should preserve the difference between an advertisement being delivered and a customer progressing through the business. Start with separate records and join only where the available evidence supports it.&lt;/p&gt;

&lt;p&gt;A small planning schema could look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;media_delivery: date, campaign_id, creative_id,
                market, impressions, spend, source
web_response:   occurred_at, event_id, event_name,
                campaign_label, source_system
crm_outcome:    lead_id, created_at, stage,
                stage_changed_at, qualification_reason
report_rules:  timezone, attribution_window,
                dedupe_rule, source_updated_at
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is a discussion aid, not a complete production schema. Platform exports, permitted identifiers and reporting granularity vary. Confirm what can actually be obtained before designing a dashboard around it.&lt;/p&gt;

&lt;p&gt;VAST belongs to the video delivery layer. IAB Tech Lab's &lt;a href="https://iabtechlab.com/standards/vast/" rel="noopener noreferrer"&gt;VAST specification&lt;/a&gt; describes communication between ad servers and video players. It does not supply the advertiser's CRM qualification rules. Treat those as separate integration responsibilities.&lt;/p&gt;

&lt;p&gt;Use a data dictionary to explain the keys that connect systems. If a campaign name changes halfway through a test, retain a mapping to a stable identifier. If no reliable match exists, report the aggregate separately instead of manufacturing a precise connection.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make reconciliation reproducible
&lt;/h2&gt;

&lt;p&gt;A reproducible report preserves source windows, transformations and deduplication rules. Another analyst should be able to explain why two totals differ without guessing.&lt;/p&gt;

&lt;p&gt;Normalize time carefully. A platform's reporting day may use a different timezone from the CRM. State which timezone defines each daily total and how late-arriving records are handled. A weekly comparison should also distinguish event date from the date the export was downloaded.&lt;/p&gt;

&lt;p&gt;For deduplication, choose a rule that matches the business process. The same person may submit twice, call after submitting or return with a different need. There is no universal rule that makes all of those records one lead. Document the chosen treatment and retain enough source lineage to review it.&lt;/p&gt;

&lt;p&gt;Keep transformation logic versioned. If the qualification rule changes, mark the effective date and explain whether earlier periods were recalculated. Otherwise an apparent improvement may be a reporting change.&lt;/p&gt;

&lt;p&gt;Use aggregate QA checks before adding visualization. Reconcile accepted submissions against the receiving system, inspect missing campaign identifiers and compare stage counts with CRM totals. Record the reasons for unresolved differences. An empty field should remain visibly unavailable until its source is fixed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build a report that states the strength of its evidence
&lt;/h2&gt;

&lt;p&gt;A useful CTV report separates observed delivery, observed response, attributed outcomes and experimental estimates. These answer different questions and deserve different labels.&lt;/p&gt;

&lt;p&gt;Suppose branded searches and enquiries rise during a campaign. That is a pattern worth investigating. Promotions, seasonality, other advertising and operational changes may also contribute. A chart showing two rising lines cannot settle the causal question by itself.&lt;/p&gt;

&lt;p&gt;If the team plans a geographic comparison or another experiment, agree the design before delivery begins. Define the outcome, comparison basis, decision window and limitations. The required data volume may make some questions impractical for a small campaign.&lt;/p&gt;

&lt;p&gt;Simplicity Media presents its &lt;a href="https://simplicitymedia.com/services/ctv-advertising-agency/" rel="noopener noreferrer"&gt;ctv advertising agency&lt;/a&gt; offering as coordinated planning, buying, creative and measurement. The engineering discussion should establish which reporting integrations belong in the engagement and which remain with the advertiser.&lt;/p&gt;

&lt;p&gt;For operating responsibilities, its &lt;a href="https://simplicitymedia.com/compare/managed-ctv-vs-self-service/" rel="noopener noreferrer"&gt;managed versus self-service CTV comparison&lt;/a&gt; can help frame the handoff. Ask who investigates broken events, maintains exports and explains revisions to a previously issued report.&lt;/p&gt;

&lt;h2&gt;
  
  
  Implementation questions worth answering early
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does a website analytics event establish CTV exposure?
&lt;/h3&gt;

&lt;p&gt;No. It records the configured website interaction. Exposure information requires a separate permitted source and a defensible method for connecting the records.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should every source be forced into one conversion total?
&lt;/h3&gt;

&lt;p&gt;No. Keep source totals available and reconcile them with explicit rules. Combining incompatible definitions can hide double counting and missing data.&lt;/p&gt;

&lt;h3&gt;
  
  
  What happens when the CRM updates a lead later?
&lt;/h3&gt;

&lt;p&gt;Preserve the stage-change timestamp and document refresh behavior. A report should explain whether it shows the latest state or the state known at a particular cutoff.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do developers need impression-level logs?
&lt;/h3&gt;

&lt;p&gt;Only if the agreed use case requires them and access permits them. Design around confirmed fields and reporting rights rather than an assumed unrestricted export.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is a useful first QA exercise?
&lt;/h3&gt;

&lt;p&gt;Trace a test enquiry from submission to receipt and qualification. Check retries, duplicate handling, timestamps and exclusions before relying on campaign totals.&lt;/p&gt;

&lt;h2&gt;
  
  
  Write the contract before the dashboard
&lt;/h2&gt;

&lt;p&gt;Begin with one page listing the events, source owners, keys, timezones and reconciliation rules. Review it with marketing and sales, then build the smallest report that answers an agreed question. Add complexity when a new decision requires it.&lt;/p&gt;

&lt;p&gt;To discuss Simplicity Media's CTV and measurement services, visit &lt;a href="https://simplicitymedia.com/" rel="noopener noreferrer"&gt;simplicitymedia.com&lt;/a&gt;. Bring the existing analytics setup, available CRM fields and a list of known tracking gaps so the integration scope can be made concrete.&lt;/p&gt;

</description>
      <category>analytics</category>
    </item>
    <item>
      <title>How to Check If ChatGPT Recommends Your Business</title>
      <dc:creator>dadev</dc:creator>
      <pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate>
      <link>https://dev.to/daviddacruz/how-to-check-if-chatgpt-recommends-your-business-fjn</link>
      <guid>https://dev.to/daviddacruz/how-to-check-if-chatgpt-recommends-your-business-fjn</guid>
      <description>&lt;p&gt;Short answer&lt;/p&gt;

&lt;h2&gt;
  
  
  Run the same buyer questions, then separate mentions, recommendations, and citations.
&lt;/h2&gt;

&lt;p&gt;Write five to ten non-branded questions a qualified buyer could ask, including the buyer type, problem, location, and constraints that affect the choice. Run the same set in a clean session across the AI products that matter to you. Save the complete answer, model, date, companies named, recommendation position, description, and visible sources. Repeat the test on a fixed schedule. One answer is an observation; repeated tests create a baseline. If you want me to prepare that baseline, &lt;a href="https://daviddacruz.dev/contact/" rel="noopener noreferrer"&gt;request a free AI Visibility Snapshot&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;01 · When to pay attention&lt;/p&gt;

&lt;h2&gt;
  
  
  The test becomes useful when it reflects an actual buying decision.
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;A founder ranks well in Google but cannot find the company in unbranded ChatGPT recommendations.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A sales or marketing team wants to know which competitors AI assistants shortlist for high-intent questions.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The company is mentioned, but the answer describes its category, audience, location, or service incorrectly.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A guide is cited without the company being recommended, or a directory is cited instead of the company website.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The team is considering AI-visibility software but has not yet defined which buyer questions deserve monitoring.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Content, technical SEO, PR, and profile work are happening, but nobody can connect those activities to a repeatable AI-answer test.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;02 · Working method&lt;/p&gt;

&lt;h2&gt;
  
  
  Measure the buyer question and the evidence trail, not whether the model can repeat your homepage.
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Business owners are asking why strong Google visibility does not automatically become an AI recommendation. The measurement problem comes first: a branded prompt is too easy, a single screenshot is too unstable, and one percentage hides the difference between being known, cited, and selected.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  Start with real buyer questions
&lt;/h3&gt;

&lt;p&gt;A useful prompt names the buyer or company type, the problem, a meaningful constraint, and the decision. For example: ‘We run a 15-person US software company. Which type of consultant should we hire to find repetitive workflows worth automating first?’ That is more diagnostic than ‘best AI consultant’ because it gives the answer system a real comparison to make. Build a small set across discovery, evaluation, and risk. Keep branded questions in a separate diagnostic group so they do not inflate non-branded visibility.&lt;/p&gt;

&lt;h3&gt;
  
  
  Control what you can repeat
&lt;/h3&gt;

&lt;p&gt;Use a clean or logged-out session when the product allows it. Put location and business context in the prompt instead of relying on hidden personalization. Keep the prompt text stable, record the product and date, and repeat important questions more than once. Model updates, browsing behaviour, session history, location, and phrasing can change an answer. A screenshot proves what happened once; a fixed method lets you compare what happens over time.&lt;/p&gt;

&lt;h3&gt;
  
  
  Record the answer before reducing it to a score
&lt;/h3&gt;

&lt;p&gt;For each run, save whether the business was named, whether it was recommended, where it appeared in the shortlist, how it was described, which URLs were cited, and which competitors appeared instead. Read the underlying answers. A 40% mention rate can hide a category error in every mention, while a low rate may be less urgent when no competitor appears consistently either. Keep the evidence available beside any aggregate score.&lt;/p&gt;

&lt;h3&gt;
  
  
  Compare evidence, not wording
&lt;/h3&gt;

&lt;p&gt;When a competitor appears, inspect what an answer can verify about both companies. Check crawlability, the clarity of core pages, first-party proof such as named work and methods, legitimate third-party corroboration, and coverage of the buyer question itself. Do not copy a competitor’s paragraph or manufacture mentions. The useful question is which missing evidence makes the competitor easier to retrieve, understand, or trust for that specific decision.&lt;/p&gt;

&lt;h3&gt;
  
  
  Turn the finding into one next action
&lt;/h3&gt;

&lt;p&gt;Fix the clearest evidence gap before publishing another general article. That may mean removing a crawler block, clarifying who a service is for, adding verifiable proof, creating the missing comparison or implementation page, improving internal links, or earning a legitimate third-party reference. Record the change and rerun the same prompt set later. The measurement is only valuable when it changes a decision.&lt;/p&gt;

&lt;p&gt;03 · Comparison&lt;/p&gt;

&lt;h2&gt;
  
  
  Track these outcomes separately before creating a visibility score.
&lt;/h2&gt;

&lt;p&gt;A single AI answer can cite your page, mention your company, and still recommend somebody else. These are different observations and they lead to different fixes.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Outcome&lt;/th&gt;
&lt;th&gt;What to record&lt;/th&gt;
&lt;th&gt;What it tells you&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Mention&lt;/td&gt;
&lt;td&gt;Whether the answer names the business and whether the description is accurate.&lt;/td&gt;
&lt;td&gt;The system can associate the company with some part of the question, but a mention is not necessarily preference or intent.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Recommendation&lt;/td&gt;
&lt;td&gt;Whether the company is first, shortlisted, mentioned in passing, or absent.&lt;/td&gt;
&lt;td&gt;The answer treats the business as a plausible choice for the buyer’s stated situation.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Citation&lt;/td&gt;
&lt;td&gt;Every visible URL attached to the answer, including company, directory, editorial, and community sources.&lt;/td&gt;
&lt;td&gt;Which retrieved pages visibly support the response. A cited guide does not guarantee the author’s service will be recommended.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Competitor evidence&lt;/td&gt;
&lt;td&gt;The companies selected instead and the pages or third-party sources that support them.&lt;/td&gt;
&lt;td&gt;The actual comparison set and the evidence gap worth investigating, rather than the competitors named in an internal strategy deck.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Practical sequence&lt;/p&gt;

&lt;h2&gt;
  
  
  Build a 30-minute AI Visibility Snapshot in six steps.
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;### Write three high-intent questions&lt;/p&gt;

&lt;p&gt;Choose questions that could precede a sale. Include the US market, company size, use case, or other constraint only when it genuinely changes the answer.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;### Run each question in two AI products&lt;/p&gt;

&lt;p&gt;Use the exact same wording in clean sessions. Save the complete answers rather than copying only the sentence that names a company.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;### Separate presence from preference&lt;/p&gt;

&lt;p&gt;Mark your business as absent, mentioned, recommended, or cited. Record description accuracy and shortlist position separately.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;### List competitors and sources&lt;/p&gt;

&lt;p&gt;Capture every recommended company and visible URL. Note whether support comes from owned pages, directories, reviews, publishers, communities, or another source type.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;### Choose one evidence gap&lt;/p&gt;

&lt;p&gt;Compare the strongest competitor with your business and select the smallest justified fix. Do not turn the snapshot into a long backlog of speculative tactics.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;### Rerun on a fixed schedule&lt;/p&gt;

&lt;p&gt;Weekly or monthly is enough for many smaller companies. Keep the core prompt set stable, date each change, and treat answer variation as part of the measurement.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;What the first snapshot should produce&lt;/p&gt;

&lt;h2&gt;
  
  
  The result should be a decision, not a vanity badge.
&lt;/h2&gt;

&lt;p&gt;A useful one-page snapshot shows where the company appears, where it does not, which competitors are selected, which sources support those answers, and the clearest next action. Start manually before buying a platform. Software becomes worthwhile when several markets, products, competitors, and more than about 20 important questions make the repeated work difficult to maintain. The tool should automate a measurement system you understand; it should not decide which customer questions matter. &lt;a href="https://daviddacruz.dev/contact/" rel="noopener noreferrer"&gt;Request the free AI Visibility Snapshot&lt;/a&gt; if you want the baseline, competitor evidence, and first action prepared for your company.&lt;/p&gt;

&lt;p&gt;Official guidance and public questions&lt;/p&gt;

&lt;h2&gt;
  
  
  The method uses product guidance for implementation and Reddit only as a demand signal.
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;a href="https://help.openai.com/en/articles/12627856" rel="noopener noreferrer"&gt;&lt;strong&gt;OpenAI publisher FAQ&lt;/strong&gt; OpenAI explains that publishers who want content included in ChatGPT search summaries should not block OAI-SearchBot and describes how ChatGPT referral traffic can be identified. Crawl access is an eligibility check, not a recommendation guarantee.&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://developers.google.com/search/docs/fundamentals/ai-optimization-guide" rel="noopener noreferrer"&gt;&lt;strong&gt;Google guidance for AI features in Search&lt;/strong&gt; Google says normal SEO fundamentals, useful original content, accessible pages, and accurate structured data remain relevant, while warning against scaled content and inauthentic mentions.&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://www.reddit.com/r/smallbusiness/comments/1rzmh96/has_anyone_else_noticed_their_business_is/" rel="noopener noreferrer"&gt;&lt;strong&gt;Reddit: Google visibility but absent from AI answers&lt;/strong&gt; A public small-business question reviewed on 9 August 2026. It is evidence of the owner’s measurement problem, not evidence about an AI ranking system.&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://www.reddit.com/r/SEO/comments/1vg54co/how_do_you_get_your_site_recommended_by_chatgpt/" rel="noopener noreferrer"&gt;&lt;strong&gt;Reddit: how to get recommended by ChatGPT&lt;/strong&gt; A public question about sources, third-party mentions, structured data, local context, and tools. Comments were not used as authoritative implementation guidance.&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://www.reddit.com/r/SEO_for_AI/comments/1uz0nwh/how_can_i_see_brand_mentions_in_chatgpt/" rel="noopener noreferrer"&gt;&lt;strong&gt;Reddit: how to track ChatGPT brand mentions&lt;/strong&gt; A public question about monitoring mentions and recommendations. The repeated need informed this measurement-first guide.&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Related reading&lt;/p&gt;

&lt;h2&gt;
  
  
  Related work and reading.
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;a href="https://daviddacruz.dev/insights/what-is-peec-ai/" rel="noopener noreferrer"&gt;What is Peec AI?→&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://daviddacruz.dev/insights/agentic-engine-optimization-aeo/" rel="noopener noreferrer"&gt;Agentic Engine Optimization→&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://daviddacruz.dev/ai-opportunity-audit/" rel="noopener noreferrer"&gt;AI Opportunity Audit→&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;  &lt;a href="https://daviddacruz.dev/insights/ai-search-optimization-glossary/" rel="noopener noreferrer"&gt;AI search terminology→&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Questions&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions about checking ChatGPT business recommendations.
&lt;/h2&gt;

&lt;h3&gt;
  
  
  How can I check whether ChatGPT recommends my business?
&lt;/h3&gt;

&lt;p&gt;Create five to ten buyer questions that do not name your company, run the same questions in a clean ChatGPT session, and record whether the business is absent, mentioned, recommended, or cited. Save the competitors and visible sources, then repeat the fixed test on a schedule.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why does ChatGPT recommend competitors when my business ranks higher on Google?
&lt;/h3&gt;

&lt;p&gt;A Google ranking and an AI recommendation are different observations. An AI answer may use multiple searches, sources, and contextual constraints. Compare the owned pages and independent evidence supporting each competitor instead of assuming one Google position should transfer directly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does schema make ChatGPT recommend a business?
&lt;/h3&gt;

&lt;p&gt;No schema type guarantees a recommendation. Accurate structured data can help a system interpret a page, but it cannot replace crawlability, clear positioning, useful content, real proof, and corroborating sources.&lt;/p&gt;

&lt;h3&gt;
  
  
  How often should a small company test AI visibility?
&lt;/h3&gt;

&lt;p&gt;Weekly or monthly is sufficient for many smaller companies. Use the same core questions, location assumptions, products, and scoring rules so the results remain comparable. Run extra tests after a meaningful site, content, product, or market change.&lt;/p&gt;

&lt;h3&gt;
  
  
  Should I pay for AI-visibility tracking software?
&lt;/h3&gt;

&lt;p&gt;Start manually so you understand which buyer questions and evidence matter. A platform becomes useful when the prompt set, models, markets, and competitor comparisons are too repetitive for a reliable manual process. Do not buy a dashboard before defining the decisions it must support.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I pay to be recommended by ChatGPT?
&lt;/h3&gt;

&lt;p&gt;You cannot buy a guaranteed organic recommendation. Paid placements and organic answers should be measured separately. Focus on making accurate public evidence easy to crawl, understand, and verify, and avoid manufactured mentions or undisclosed paid links.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>chatgpt</category>
      <category>seo</category>
      <category>business</category>
    </item>
    <item>
      <title>Claude Code Skills &amp; Agents: Build Custom Slash Commands for Real Work</title>
      <dc:creator>dadev</dc:creator>
      <pubDate>Sun, 26 Apr 2026 17:57:06 +0000</pubDate>
      <link>https://dev.to/daviddacruz/claude-code-skills-agents-build-custom-slash-commands-for-real-work-3865</link>
      <guid>https://dev.to/daviddacruz/claude-code-skills-agents-build-custom-slash-commands-for-real-work-3865</guid>
      <description>&lt;p&gt;Claude Code is powerful out of the box. Skills and subagents turn it into a steadier system: reusable commands, specialised agents, and workflows that scale with your codebase.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Are Claude Code Skills?
&lt;/h2&gt;

&lt;p&gt;If you've used Claude Code for more than a week, you've probably noticed a pattern: you type the same kinds of instructions over and over. "Review this PR with focus on security." "Deploy to staging and run smoke tests." "Refactor this component using the patterns from our design system."&lt;/p&gt;

&lt;p&gt;Skills solve this. A skill is a reusable slash command that gives Claude specific instructions for a task. Instead of typing a paragraph every time you want Claude to do something, you type &lt;code&gt;/deploy&lt;/code&gt; or &lt;code&gt;/review-pr&lt;/code&gt; and it knows exactly what to do, how to do it, and what standards to follow.&lt;/p&gt;

&lt;p&gt;Think of skills as project runbooks for Claude: markdown files, version-controlled alongside your code, and shared across the team. They follow the Agent Skills open standard, which means the pattern can travel beyond Claude Code.&lt;/p&gt;

&lt;p&gt;This matters because the biggest productivity drain with AI coding assistants isn't the AI's capability. It's the context you have to provide every single time. Skills eliminate that friction entirely.&lt;/p&gt;

&lt;p&gt;::callout&lt;br&gt;
&lt;strong&gt;Key takeaway:&lt;/strong&gt; Skills are reusable slash commands stored as markdown files. They encode your team's standards, workflows, and context so you don't have to repeat yourself. Type &lt;code&gt;/deploy&lt;/code&gt; instead of explaining your deployment process every time.&lt;br&gt;
::&lt;/p&gt;

&lt;h2&gt;
  
  
  Anatomy of a Skill
&lt;/h2&gt;

&lt;p&gt;Every skill lives in a &lt;code&gt;SKILL.md&lt;/code&gt; file. It has two parts: YAML frontmatter that tells Claude when and how to use the skill, and markdown content with the actual instructions Claude follows when the skill is invoked.&lt;/p&gt;

&lt;p&gt;You can store skills in two places. Global skills go in &lt;code&gt;~/.claude/skills/&lt;/code&gt; and are available in every project. Project skills go in &lt;code&gt;.claude/skills/&lt;/code&gt; within your repository and are shared with anyone who clones the repo.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Frontmatter
&lt;/h3&gt;

&lt;p&gt;The frontmatter is where you configure how the skill behaves. The &lt;code&gt;name&lt;/code&gt; field sets the slash command name. The &lt;code&gt;description&lt;/code&gt; tells Claude (and your team) what the skill does. The &lt;code&gt;invocation&lt;/code&gt; field controls when the skill triggers — &lt;code&gt;user&lt;/code&gt; means it only runs when explicitly called, while &lt;code&gt;auto&lt;/code&gt; lets Claude invoke it when it detects a matching situation.&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;agent&lt;/code&gt; field is where things get interesting. You can specify which subagent configuration to use — built-in agents like &lt;code&gt;Explore&lt;/code&gt; or &lt;code&gt;Plan&lt;/code&gt;, or any custom subagent you've defined in &lt;code&gt;.claude/agents/&lt;/code&gt;. This lets you create skills that delegate to specialized agents optimized for specific tasks.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Instructions
&lt;/h3&gt;

&lt;p&gt;Below the frontmatter, you write plain markdown instructions. These are injected as Claude's system prompt when the skill runs. You can include step-by-step procedures, code patterns to follow, validation checks, and references to project files.&lt;/p&gt;

&lt;p&gt;The power here is specificity. A generic instruction like "review this code" produces generic results. A skill that says "check for SQL injection in any raw query, verify all user inputs pass through our sanitization middleware, flag any use of &lt;code&gt;eval()&lt;/code&gt; or &lt;code&gt;Function()&lt;/code&gt;, and cross-reference against our OWASP checklist at &lt;code&gt;docs/security.md&lt;/code&gt;" produces consistently excellent results.&lt;/p&gt;

&lt;h2&gt;
  
  
  Built-in Skills Worth Knowing
&lt;/h2&gt;

&lt;p&gt;Claude Code ships with a set of bundled skills that are available in every session. These are worth learning before you start building your own, because they cover the most common workflows and serve as excellent templates.&lt;/p&gt;

&lt;h3&gt;
  
  
  /commit
&lt;/h3&gt;

&lt;p&gt;Analyzes staged changes, drafts a commit message following your repo's conventions, and creates the commit. It reads recent commit history to match your style. Sounds simple, but it eliminates the context switch between coding and committing, and it produces consistently better commit messages than most developers write under time pressure.&lt;/p&gt;

&lt;h3&gt;
  
  
  /simplify
&lt;/h3&gt;

&lt;p&gt;Reviews recently changed code for reuse opportunities, quality issues, and efficiency improvements. This is the skill I run after every significant implementation — it catches the abstractions you missed and the edge cases you forgot while focused on making the happy path work.&lt;/p&gt;

&lt;h3&gt;
  
  
  /loop
&lt;/h3&gt;

&lt;p&gt;Runs a prompt or slash command on a recurring interval. You can set a fixed interval like &lt;code&gt;/loop 5m /deploy-check&lt;/code&gt; or let Claude self-pace. This is how you build monitoring workflows — watching a build, polling for deployment status, or periodically checking test results while you work on something else.&lt;/p&gt;

&lt;h3&gt;
  
  
  /review-pr
&lt;/h3&gt;

&lt;p&gt;Fetches a pull request, analyzes every commit, checks for security issues, tests coverage gaps, and provides structured feedback. Combine this with project-specific rules in your &lt;code&gt;CLAUDE.md&lt;/code&gt; and you get code review that enforces your team's standards automatically.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building Your Own Skills
&lt;/h2&gt;

&lt;p&gt;The built-in skills are useful, but the real power is in building skills tailored to your project. Here's the framework I use when creating custom skills for teams.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 1 — Identify the Repetition
&lt;/h3&gt;

&lt;p&gt;Look at your last 20 Claude Code conversations. What instructions did you type more than twice? What context did you keep providing? Those are your skill candidates. Common patterns: deployment procedures, code review checklists, migration steps, component scaffolding, and test writing conventions.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2 — Write the Instructions
&lt;/h3&gt;

&lt;p&gt;Write your skill instructions as if you're briefing a senior developer who just joined the team. They're smart but they don't know your project. Be explicit about file paths, naming conventions, testing requirements, and what "done" looks like. Vague skills produce vague results.&lt;/p&gt;

&lt;p&gt;Include references to your project's documentation. If you have a style guide at &lt;code&gt;docs/style.md&lt;/code&gt;, tell the skill to read it. If there's a component template at &lt;code&gt;templates/component.vue&lt;/code&gt;, point to it. The more grounded your skill is in actual project artifacts, the better the output.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3 — Set the Right Invocation
&lt;/h3&gt;

&lt;p&gt;Use &lt;code&gt;invocation: user&lt;/code&gt; for skills that should only run when explicitly called — deployment, database migrations, anything with side effects. Use &lt;code&gt;invocation: auto&lt;/code&gt; for skills that should fire when Claude detects a matching pattern — like automatically applying your component naming convention when it sees you creating a new component.&lt;/p&gt;

&lt;p&gt;Auto-invoked skills are powerful but use them carefully. A skill that fires when you don't expect it is worse than no skill at all.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4 — Commit and Share
&lt;/h3&gt;

&lt;p&gt;Put project-specific skills in &lt;code&gt;.claude/skills/&lt;/code&gt; and commit them. Now every developer on the team has the same slash commands, the same standards enforcement, and the same workflow shortcuts. This is how you scale AI-assisted development beyond individual productivity — you encode your team's collective intelligence into reusable commands.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"The biggest productivity drain with AI coding assistants isn't the AI's capability. It's the context you have to provide every single time. Skills eliminate that friction entirely."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Agents and Subagents
&lt;/h2&gt;

&lt;p&gt;Skills tell Claude &lt;em&gt;what&lt;/em&gt; to do. Agents control &lt;em&gt;how&lt;/em&gt; it does it. Claude Code's agent system lets you spawn specialized subagents — isolated instances that handle specific parts of a task with their own tools, context, and instructions.&lt;/p&gt;

&lt;p&gt;The built-in agents cover the most common patterns. &lt;strong&gt;Explore&lt;/strong&gt; is optimized for codebase navigation — fast file searching, pattern matching, and understanding project structure. &lt;strong&gt;Plan&lt;/strong&gt; is a software architect agent that designs implementation strategies, identifies critical files, and considers trade-offs before you write any code. The &lt;strong&gt;general-purpose&lt;/strong&gt; agent handles everything else.&lt;/p&gt;

&lt;p&gt;But the real power is in custom agents. You define them in &lt;code&gt;.claude/agents/&lt;/code&gt; with their own system prompts, tool access, and behavioral constraints. A security-review agent that only has read access and focuses exclusively on vulnerability patterns. A migration agent that understands your database schema and ORM conventions. A documentation agent that reads your code and generates docs matching your existing style.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why Subagents Matter
&lt;/h3&gt;

&lt;p&gt;Subagents aren't just about parallelism. They're about &lt;strong&gt;context isolation&lt;/strong&gt;. When you ask Claude to do ten things in one conversation, context bleeds between tasks. The code review influences the refactoring. The deployment check changes how it writes tests.&lt;/p&gt;

&lt;p&gt;Subagents solve this by running in isolation. Each one gets a clean context window, focused instructions, and only the tools it needs. The results flow back to the main conversation, but the work happens in a controlled environment. This is the same principle behind microservices — bounded contexts produce better results than monolithic processes.&lt;/p&gt;

&lt;p&gt;A skill can specify &lt;code&gt;agent: my-custom-agent&lt;/code&gt; in its frontmatter, and now your slash command delegates to a specialized agent. &lt;code&gt;/security-scan&lt;/code&gt; spawns your security agent. &lt;code&gt;/plan-feature&lt;/code&gt; spawns your architecture agent. The skill provides the instructions; the agent provides the execution environment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Real-World Skill Patterns
&lt;/h2&gt;

&lt;p&gt;Here are the skill patterns I've found most valuable across different projects. These aren't hypothetical — they're running in production codebases right now.&lt;/p&gt;

&lt;h3&gt;
  
  
  Component Scaffolding
&lt;/h3&gt;

&lt;p&gt;A skill that creates new components following your exact project conventions. It reads your existing component templates, applies your naming patterns, sets up the test file structure, and adds the component to your barrel exports. What used to be 15 minutes of boilerplate becomes &lt;code&gt;/new-component Button&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Database Migration Validator
&lt;/h3&gt;

&lt;p&gt;Before running any migration, this skill checks for destructive changes, verifies rollback scripts exist, validates that the migration is compatible with zero-downtime deployment, and tests it against a schema snapshot. It catches the migration that drops a column you're still reading from in production — before it reaches staging.&lt;/p&gt;

&lt;h3&gt;
  
  
  Release Notes Generator
&lt;/h3&gt;

&lt;p&gt;Reads the git log since the last tag, categorizes changes by type (feature, fix, chore), pulls PR descriptions for context, and generates release notes in your team's format. Some teams want changelogs. Others want Slack-friendly summaries. The skill encodes whatever format your team uses.&lt;/p&gt;

&lt;h3&gt;
  
  
  Incident Response Runbook
&lt;/h3&gt;

&lt;p&gt;When something breaks at 2 AM, the last thing you want is to remember the exact sequence of diagnostic commands. This skill takes an error description, checks logs, identifies the likely service, runs your standard diagnostics, and produces a structured incident report — all from &lt;code&gt;/incident "API returning 503 on /users endpoint"&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Agent Skills Open Standard
&lt;/h2&gt;

&lt;p&gt;Claude Code skills follow the Agent Skills open standard. This is worth understanding because it means your investment in writing skills isn't locked into a single tool. The same &lt;code&gt;SKILL.md&lt;/code&gt; files work across compatible AI tools — your skills are portable.&lt;/p&gt;

&lt;p&gt;Claude Code extends the standard with additional features like invocation control, subagent execution, and dynamic context injection. But the base format is interoperable. If you switch tools or use multiple AI assistants across your team, your skills library travels with you.&lt;/p&gt;

&lt;p&gt;This is also why skills belong in your repository, not in a personal config. They're project artifacts just like your CI configuration, your linting rules, and your testing standards. They codify how your team works — and they should evolve alongside your code.&lt;/p&gt;

&lt;p&gt;The teams I work with who get the most out of Claude Code share one trait: they treat their &lt;code&gt;.claude/&lt;/code&gt; directory as seriously as their &lt;code&gt;src/&lt;/code&gt; directory. Skills are code. Version them. Review them. Iterate on them. The compound returns are enormous.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources and Further Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.anthropic.com/en/docs/claude-code/overview" rel="noopener noreferrer"&gt;Claude Code overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.anthropic.com/en/docs/claude-code/sub-agents" rel="noopener noreferrer"&gt;Claude Code subagents documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.claude.com/en/docs/agents-and-tools/agent-skills" rel="noopener noreferrer"&gt;Claude Agent Skills documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://modelcontextprotocol.io/" rel="noopener noreferrer"&gt;Model Context Protocol documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;Skills plug directly into the broader stack of &lt;a href="https://daviddacruz.dev/blog/ai-automation-workflows-for-business" rel="noopener noreferrer"&gt;AI automations for business&lt;/a&gt;: research agents, outreach pipelines, and support triage workflows. If you are building these systems for a team and want a partner who treats them as infrastructure, start with the &lt;a href="https://daviddacruz.dev/services/ai-automation" rel="noopener noreferrer"&gt;AI automation service&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>developertools</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
