application-artifact

Public job application artifacts are alternative deliverables like teardown posts, pull requests, or benchmarks used instead of low-signal job applications. Use them when a target company's artifact fit is strong or optional and you have a defined artifact idea to build.

To scope and track a job application artifact, define the deliverable, success criteria, time budget, and kill criteria. The skill creates an artifact.md file with structured metadata, enforces guardrails, and logs artifact_shipped events upon completion.

Choosing the right artifact type involves selecting among teardown posts, pull requests, tools or extensions, and benchmarks based on company fit. The skill guides flavor selection by evaluating whether the company's artifact_fit is strong or optional.

Yes, you can manage time budgets and kill criteria for job application projects. The skill enforces guardrails during scope definition, ensuring disciplined delivery by generating concrete deliverables and time-budget constraints within the artifact.md file.

To log completed job application artifacts, the skill uses the repository logging command to record artifact_shipped events. This happens after you finish building the deliverable and update the structured metadata in artifact.md.

The best way to replace low-signal job applications is building public artifacts with defined scopes and success criteria. This approach prevents ad-hoc effort by organizing creation, scoping, and tracking through structured metadata and enforced guardrails.