journal-entry-import
Reconstructs journal entries from external systems: bulk-imports a historical work log from a legacy source system such as a deprecated Confluence page into dated entries, enriches ticket references with self-contained detail entries reconstructed from an issue tracker, and annotates links to systems that have since moved such as a Bitbucket-to-GitLab migration. Use when asked to import an old journal, migrate a log into the journal format, turn ticket mentions into entries, expand a log with ticket detail, or point old links at a new host. This is not for repairing frontmatter on entries that already exist in this format, which is the journal CLI's own backfill command. Produces validated dated entries compatible with journal-entry-creator, complete with bidirectional cross-links and annotated external links.
72
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow ingests outsider-authored issue tracker tickets and comments (Mode B) and legacy wiki pages (Mode A), where an outsider can submit free text into monitored sources.
- Repository
- pantheon-org/tekhne
- Commit
a1083f4
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.