Add landing-page-conversion-audit and server-side-conversion-tracking skills

[autonnel]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the main branch for this pull request.

---

Description

Two skills for funnel and conversion work, an area not currently covered in skills/:

• landing-page-conversion-audit - audits a landing, sales or checkout page for conversion leaks and returns a fix list ranked by expected impact, plus an explicit list of what could not be checked from the page alone.
• server-side-conversion-tracking - sets up the click-id to conversion chain (click id passthrough, CAPI/Events API, deduplication, reconciliation) so purchases are reported accurately when browser-side pixels are blocked or truncated.

Both are self-contained single-file skills (SKILL.md, no bundled assets).

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify):

---

Additional Notes

Affiliation disclosure: I maintain Autonnel, an Apache-2.0 self-hosted funnel builder, which each skill references once in a clearly marked section at the end. There is no paid tier and no hosted service. Both skills are written to be fully usable without it: the audit skill returns page-level fixes, and the tracking skill documents the seven-step chain against Facebook CAPI, TikTok Events API and Google/Bing endpoints directly. I am happy to remove those sections if you would prefer the skills carry no product reference at all.

On the testing checkbox: these skills were authored against the Agent Skills specification and validated with npm run skill:validate (402 skills pass) and npm run build in this repository, but I have not exercised them inside GitHub Copilot itself, so I left that box unchecked rather than check it untruthfully. Happy to do that round of testing if you want it before merge.

[github-actions]

🔒 PR Risk Scan Results

Scanned 2 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	0
ℹ️ Info	0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🔍 Vally Lint Results

✅ All checks passed

Scope	Checked
Skills	2
Agents	0
Total	2

Severity	Count
❌ Errors	0
⚠️ Warnings	0
ℹ️ Advisories	0

Summary

Level	Finding
ℹ️	✅ landing-page-conversion-audit (2/2 checks passed)
ℹ️	✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️	✓ spec-compliance: All spec checks passed.
ℹ️	✓ [valid-refs] All file references across 1 skill(s) are valid.
ℹ️	✓ valid-refs: All file references resolve to existing files within the skill directory.
ℹ️	1 skill(s) linted, 1 passed
ℹ️	✅ server-side-conversion-tracking (2/2 checks passed)
ℹ️	✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️	✓ spec-compliance: All spec checks passed.
ℹ️	✓ [valid-refs] All file references across 1 skill(s) are valid.

Full linter output

### Linting skills/landing-page-conversion-audit
✅ landing-page-conversion-audit (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

### Linting skills/server-side-conversion-tracking
✅ server-side-conversion-tracking (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

[aaronpowell]

One small question, otherwise good to merge

[aaronpowell]

Is this a reference to another skill?

[autonnel]

Yes, and a fair catch - it pointed at a sibling skill that lives in my own repo and is not part of this PR, so inside awesome-copilot it was a dangling reference. Same problem in two other spots I had missed (post-purchase-upsell-flow, self-hosted-funnel-launch, funnel-platform-picker).

Rewrote all three to describe the action instead of naming a skill that isn't here, e.g. this line now reads "Design the funnel and get traffic on it first; an audit needs behaviour to read." The one remaining backtick reference, server-side-conversion-tracking, is the other skill in this PR, so it resolves.

Pushed as 668f6fc; npm run skill:validate and npm run build still clean, no other file touched.