feat(ultimate-scraper): tag CLI invocations with --user-agent for telemetry attribution#42
Merged
vystrcild merged 1 commit intoApr 28, 2026
Conversation
…emetry attribution Adds --user-agent apify-agent-skills/apify-ultimate-scraper to every apify CLI example in the apify-ultimate-scraper skill (SKILL.md, gotchas.md, actor-index.md, and four workflow guidance files), plus a top-level rule in SKILL.md documenting the convention. Bumps the CLI prerequisite to v1.5.0+ since the flag was introduced in apify/apify-cli#1102. This lets us distinguish skill-driven CLI invocations from generic human usage in Mixpanel/Segment via properties.userAgent, and aligns with the existing apify-agent-skills/<slug> naming convention used in actor_run.meta_user_agent data feeding dashboards.apify.com/dashboards/276. Refs: apify/apify-cli#1102 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collaborator
|
Tested, working! 👍 @lukas-bekr Did you test how the data are attributed to the runs? Will we be able to see it in Actor Runs or does CLI works differently? |
vystrcild
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--user-agent apify-agent-skills/apify-ultimate-scraperto everyapifyCLI example across the skill: 8 inSKILL.md, 8 inserts (across 7 example locations) inreferences/gotchas.md, 1 inreferences/actor-index.md, and 4 inline mentions in workflow guidance files (company-research, ecommerce-price-monitoring, job-market-and-recruitment, real-estate-and-hospitality).SKILL.md(alongside the existing--jsonrule) so agents that construct ad-hoc commands still emit the flag.v1.4.0+→v1.5.0+(the flag was merged in apify/apify-cli#1102 and shipped inv1.5.0).Why
The CLI now emits a caller-id field (
properties.userAgent) on everycli_command_*Segment event. Tagging skill-driven invocations lets us measure agent-skills usage in Mixpanel separately from generic human CLI usage. Value matches the existingapify-agent-skills/<slug>naming convention so future cross-pipeline continuity is automatic.Scope
apify-ultimate-scraperis instrumented in this PR. Development-focused skills (apify-actor-development,apify-actorization,apify-generate-output-schema) will be tagged separately.actorentrypoint, which the skill never invokes — non-issue.🤖 Generated with Claude Code